The ops and reference implementation for Apache Dubbo
polarbear567/k8s-git-autodeploy 0
This tool can help you manage the yaml (JSON) files in Git and automatically deploy them to the k8s cluster, so as to realize file to version control, facilitate team management and avoid manual deployment.
Production-Grade Container Scheduling and Management
Spring Boot
polarbear567/spring-framework 0
Spring Framework
push eventpolarbear567/k8s-git-autodeploy
commit sha 78e4c28b59ede72cd73d51df5e8e09382b74d426
Update README.md
push time in 2 months
push eventpolarbear567/k8s-git-autodeploy
commit sha dbe286daab38058c208bbc837b4d6f427cd22e97
init
push time in 2 months
push eventpolarbear567/k8s-git-autodeploy
commit sha 869732220b3c94c1a07206bc1a78969f3495456c
Delete README.md
push time in 2 months
created repositorypolarbear567/k8s-git-autodeploy
This tool can help you manage the yaml (JSON) files in Git and automatically deploy them to the k8s cluster, so as to realize file to version control, facilitate team management and avoid manual deployment.
created time in 2 months
push eventpolarbear567/spring-boot
commit sha c13385ea7471783c5e50afd5c504dd42a662927e
Use Awaitility instead of Thread.sleep See gh-21988
commit sha 41173f7c4019e69400c0789def787e29be543e29
Polish "Use Awaitility instead of Thread.sleep" See gh-21988
commit sha f6560830073901599f90b46e73d3b4bb1517501b
Merge pull request #21988 from tszmytka * gh-21988: Polish "Use Awaitility instead of Thread.sleep" Use Awaitility instead of Thread.sleep Closes gh-21988
commit sha 1e97ff834e2cf303c152ca91be33b0cc067b0729
Only consider current context when finding lifecycle processor Previously, LifecycleAutoConfiguration would check the current context and all of its ancestors for a lifecycle processor bean, only configuring a custom processor if one was not found. Every context has a lifecycle processor so this check meant that lifecycle processing timeout could not be customized in any context with a parent. This commit updates the auto-configuration to only check the current context. Closes gh-22014
commit sha c37fd865c00cc04f9209ac23111b599a930979d2
Merge branch '2.3.x' Closes gh-22019
commit sha 136c9b1af835d189b4c031139287919101350ebc
Merge branch '2.2.x' into 2.3.x Closes gh-22020
commit sha ca76b60de2e616ac2105f4b342dc871419b2cd11
Merge branch '2.3.x' Closes gh-22021
commit sha 627c0b1031334299905d6aa804333529a17ce1ad
Document how to exclude an annotation processor with Maven See gh-22000
commit sha 9b803af3c3e29c255815581f16a33c879ecbd82f
Polish "Document how to exclude an annotation processor with Maven" See gh-22000
commit sha 97af782ee6952423ed2e07ec50ba6262378fdf18
Merge pull request #22000 from mla-mpensdavila * pr/22000: Polish "Document how to exclude an annotation processor with Maven" Document how to exclude an annotation processor with Maven Closes gh-22000
commit sha d5385a7b6476337fde6189b5341d86320df1aaee
Merge branch '2.2.x' into 2.3.x Closes gh-22023
commit sha ea63984f935595c183783d27aa31a615c63752ab
Merge branch '2.3.x' Closes gh-22024
commit sha b218a89862e7515b6b6f743847ac8b0a5829b2d7
Remove Javadoc throw for ConfigurationPropertyName.ofIfValid() See gh-22018
commit sha f961043f362939a512605ba29fd1fce6d40bf40c
Merge pull request #22018 from izeye * pr/22018: Remove Javadoc throw for ConfigurationPropertyName.ofIfValid() Closes gh-22018
commit sha 51e9a5dae0607f41ca761cdc75dd8b89cf7a838d
Merge branch '2.3.x' Closes gh-22029
commit sha a6e85613913408ab3f5f00876abcc51cc0848db4
Catch more generic FileSystemException in NamedPipeSocket See gh-22035
commit sha d5e667f2869ce174307d7f361b65d37e708397e1
Merge pull request #22035 from dreis2211 * gh-22035: Catch more generic FileSystemException in NamedPipeSocket Closes gh-22035
commit sha 39b2d015412738178bf1ac834853c3b22f2efd00
Merge branch '2.3.x' Closes gh-22037
commit sha 73aa8f1434701930c349ff32bd6a0391dd58127b
Enforce spring-boot-parent's platform dependencies Closes gh-22047
commit sha 632d9bab216f5c750d35d9e2862c885e8112710d
Merge branch '2.3.x' Closes gh-22048
push time in 2 months
push eventpolarbear567/spring-boot
commit sha c13385ea7471783c5e50afd5c504dd42a662927e
Use Awaitility instead of Thread.sleep See gh-21988
commit sha 41173f7c4019e69400c0789def787e29be543e29
Polish "Use Awaitility instead of Thread.sleep" See gh-21988
commit sha f6560830073901599f90b46e73d3b4bb1517501b
Merge pull request #21988 from tszmytka * gh-21988: Polish "Use Awaitility instead of Thread.sleep" Use Awaitility instead of Thread.sleep Closes gh-21988
commit sha 627c0b1031334299905d6aa804333529a17ce1ad
Document how to exclude an annotation processor with Maven See gh-22000
commit sha 9b803af3c3e29c255815581f16a33c879ecbd82f
Polish "Document how to exclude an annotation processor with Maven" See gh-22000
commit sha 97af782ee6952423ed2e07ec50ba6262378fdf18
Merge pull request #22000 from mla-mpensdavila * pr/22000: Polish "Document how to exclude an annotation processor with Maven" Document how to exclude an annotation processor with Maven Closes gh-22000
commit sha 39a853c57b4ed6612a6c4e31e66de65139d0fe83
Fix infinite loop in FieldValues Update `FieldValues` test object so that it doesn't cause an infinite loop if it is actually created. See gh-22040
commit sha 3b3a49db1f55f6842ce104df710caabfd0e77843
Polish 'Fix infinite loop in FieldValues' See gh-22040
commit sha bf04baba735ea665a5948aaf39d56e40acb1e4c2
Merge pull request #22040 from Konrado85 * pr/22040: Polish 'Fix infinite loop in FieldValues' Fix infinite loop in FieldValues Closes gh-22040
commit sha 10de88884f70d342eb7d5c31a251a63d69fadb1f
Inherit show-details property in health groups Update `Group` properties so that the `showDetails` value does not inherit `Show.NEVER`. Prior to this commit, the `Group` properties would not correctly inherit a `showDetails` value from the main `management.endpoint.health.show-details` property. See gh-22022
commit sha e6eb02603c3dd26d127057ce203b5638c2273074
Polish 'Inherit show-details property in health groups' Rework the inheritance so that the property metadata JSON more accurately reflects the default value. See gh-22022
commit sha a49156d95ef6ece413abbecfe7b9df0fea60c385
Merge pull request #22022 from polarbear567 * pr/22022: Polish 'Inherit show-details property in health groups' Inherit show-details property in health groups Closes gh-22022
commit sha 0b4533659fc07a69c46f9e250f684a4fd6d5a794
Use Groovy's bom in spring-boot-dependencies Closes gh-22084
commit sha 3fed27fd90e7e35b86a9bed1b478f572c0f56507
Merge branch '2.1.x' into 2.2.x Closes gh-22085
commit sha b27303704f3c9e5adcd2cda8a7b208d290daa388
Fix RedisReactiveHealthIndicator in clustered configuration Prior to Spring Data Redis version 2.2.8, the contents of the Properties object returned from the ReactiveRedisConnection.ServerCommands.info API were the same for clustered and non-clustered Redis configurations, containing a set of key/value pairs. This allowed ReactiveRedisHealthIndicator to get a version property using a well-known key. Starting with Spring Data Redis 2.2.8, the info property keys contain a host:port prefix in a clustered Redis configuration. This prevented ReactiveRedisHealthIndicator from getting the version property as before and resulted in the health always being reported as DOWN. This commit adjusts ReactiveRedisHealthIndicator to detect the clustered configuration from Spring Data Redis and find the version property for one of the reported cluster nodes. Fixes gh-22061
commit sha 5475f10657d1e4a3e9d819728ef1db6d0550f5b8
Remove WebClient's in-memory buffer size limit for endpoint tests Previously, the thread dump endpoint's response could exceed WebClient's in-memory buffer limt when there were a large number of threads or the threads had large stacks. This commit disables WebClient's in-memory buffer size limit so that the test passing is not dependent on the number of active threads and their stack sizes. Closes gh-22101
commit sha 4a55a414e72e563222ffb57460dd6b82f9a0189a
Fix typo
commit sha 67060731bc8a6fb4bb1702c9fb0904224b1d1997
Merge branch '2.1.x' into 2.2.x
commit sha c1b9d3c2260d3c5bae733067da4f4d5ac1783e5f
Simplify logic in ErrorPage's equals method See gh-22082
commit sha 9c732fa2b632e8c4c047981d1179c3e474954a6f
Merge pull request #22082 from thenx-wei * pr/22082: Simplify logic in ErrorPage's equals method Closes gh-22082
push time in 2 months
push eventpolarbear567/kubernetes
commit sha 83b850cd54295060ee1a66b4a9e90f54cc0bb0e1
kube-aggregator/openapi/controller: remove trailing 1 in failure rate limiter
commit sha 3f043dd8a06a553de91e1bfb84500d66daf97e18
Sort init container statuses using non-nested loop
commit sha c20721aa9f0a69f267f899ca387fdc489cfe6f24
storage: enhance test for ValidateCSIDriverUpdate This revised test changes one field at a time in various ways. This ensures that one failure reason doesn't mask the other. An incorrect comment also gets fixed. Suggested in https://github.com/kubernetes/kubernetes/pull/80568#pullrequestreview-272836101.
commit sha fca84c02bb5a089d071e608a200b7dc5dc79d074
add dashpole as kubelet approver
commit sha 31ea600b284515dd3470b244f9c6e1548408ecfe
images: Adds GOARM to images' Makefiles In order to build the image binaries, the GOARM variable is required, but not all Makefiles have it defined, causing the make to fail on those images. This adds the require GOARM variable to the Makefiles in question.
commit sha 2293b473464a78877a57bdfff5a2b0f11c3283bf
add some comments for const variable
commit sha 34fce9faee46e38adf55255a77188120f2567d03
Fix a comment in job_controller
commit sha d634ed3850ff1980f21590eee051d4428acf4601
Removed unnecessary not nil check in node registration process
commit sha eb6c7169276a1978b851deafb25b507caf696ac4
PodTolerationRestriction: Mention Whitelist Scope in Error Currently it's not clear if the issue came from the namespace whitelist of if the namespace whitelist was not applied at all (i.e. via a misspelled annotation). This makes the error more explicit if the pod tolerations caused a conflict with cluster-level or namespace-level whitelist. Signed-off-by: Manuel Rüger <[email protected]>
commit sha fbb1f23735aa26c61305ff1337a02a8add830142
kube-aggregator: changes the name of aggregator_unavailable_apiservice_count metrics
commit sha f5080850fc7fd1997cb8c0be32a3f4e0e26b9c23
Delete TODO in `image_gc_manager` I think the TODO here may have actually been unnecessary. There isn't a ton of interest around merging https://github.com/kubernetes/kubernetes/pull/87425, which contains a fix. Delete the TODO so we don't devote time to working on this area in the future.
commit sha 1c393c73a63fedbcd041f21cc1a9a59de83167cb
Change SCTPSupport default value to true
commit sha 77ca434ec378d607fee83dc790eb8981d5beb4e7
Fix the newName field name in the example
commit sha c39c64ffdaf677d09c412e7447b5bf400394068b
Fix the newName field name in the page
commit sha 18856dace935db46d3ba84374ce23438922e272b
Add DNS1123Label validation to IsFullyQualifiedDomainName func This patch adds IsDNS1123Label validation to IsFullyQualifiedDomainName func. Even when one label is longer than 64 characters, the current validation does not validate it. Hence this patch adds the label check and do not allow invalid domain.
commit sha cb87793d57f59b9ead730fb1e4ed6cfa38c189f2
Add unit test to portallocator storage Add unit test for the portallocator storage based on the ipallocator ones. pkg/registry/core/service/ipallocator/storage/storage_test.go
commit sha e3df13439a72888cd83ed9896359d75e1787d2fc
fix service allocation concurrency issues The service allocator is used to allocate ip addresses for the Service IP allocator and NodePorts for the Service NodePort allocator. It uses a bitmap backed by etcd to store the allocation and tries to allocate the resources directly from the local memory instead from etcd, that can cause issues in environment with high concurrency. It may happen, in deployments with multiple apiservers, that the resource allocation information is out of sync, this is more sensible with NodePorts, per example: 1. apiserver A create a service with NodePort X 2. apiserver B deletes the service 3. apiserver A creates the service again If the allocation data of apiserver A wasn't refreshed with the deletion of apiserver B, apiserver A fails the allocation because the data is out of sync. The Repair loops solve the problem later, but there are some use cases that require to improve the concurrency in the allocation logic. We can try to not do the Allocation and Release operations locally, and try instead to check if the local data is up to date with etcd, and operate over the most recent version of the data.
commit sha d42ccdc690f617cd55da0e3f699194e1dc247895
Add myself to staging repo SECURITY_CONTACTS
commit sha 862c30a2284a54a8c91778828b41f157b6a506ec
[Provider/Azure] optimize mutex locks
commit sha 75af2fca6125516dff42e9825ceea89367986f78
add labels to diff command
push time in 3 months