- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 28 for regenerated (0.26 sec)
-
common-protos/k8s.io/api/core/v1/generated.proto
package k8s.io.api.core.v1; import "k8s.io/apimachinery/pkg/api/resource/generated.proto"; import "k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto"; import "k8s.io/apimachinery/pkg/runtime/generated.proto"; import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto"; import "k8s.io/apimachinery/pkg/util/intstr/generated.proto"; // Package-wide variables from generator "generated". option go_package = "k8s.io/api/core/v1";
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 255.8K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.20.md
- Kubeadm now makes sure the etcd manifest is regenerated upon upgrade even when no etcd version change takes place ([#94395](https://github.com/kubernetes/kubernetes/pull/94395), [@rosti](https://github.com/rosti)) [SIG Cluster Lifecycle]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jan 19 21:05:45 UTC 2022 - 409K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.11.md
combined PEM file that was atomically rotated as `kubelet-client-DATE.pem` in that directory, which meant clients relying on the `node.kubeconfig` generated by bootstrapping would never use a rotated cert. The initial bootstrap certificate is now generated into the cert directory as a PEM file and symlinked to `kubelet-client-current.pem` so that the generated kubeconfig remains valid after rotation. ([#62152](https://github.com/kubernetes/kubernetes/pull/62152), [@smarterclayton](https://github.com/smarterclayton))...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Feb 06 06:04:15 UTC 2020 - 328.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.18.md
#### client-go:
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jun 16 17:18:28 UTC 2021 - 373.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.8.md
* Action required: * Anyone who generated server cert for admission webhooks need to regenerate the cert. Previously, when generating server cert for the admission webhook, the CN value doesn't matter. Now you must set it to the DNS name of the webhook service, i.e., `<service.Name>.<service.Namespace>.svc`.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Tue Feb 20 15:45:02 UTC 2024 - 312.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
- Api: validation of a `PodSpec` now rejects invalid `ResourceClaim` and `ResourceClaimTemplate` names. For a pod, the name generated for the `ResourceClaim` when using a template also must be valid. ([#116576](https://github.com/kubernetes/kubernetes/pull/116576), [@pohly](https://github.com/pohly))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Jul 17 07:48:22 UTC 2024 - 466.3K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.16.md
- Added metrics `authentication_attempts` that can be used to understand the attempts of authentication. ([#81509](https...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Feb 11 10:00:57 UTC 2021 - 345.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.9.md
* Action required: * Anyone who generated server cert for admission webhooks need to regenerate the cert. Previously, when generating server cert for the admission webhook, the CN value doesn't matter. Now you must set it to the DNS name of the webhook service, i.e., `<service.Name>.<service.Namespace>.svc`.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Tue Nov 16 10:46:27 UTC 2021 - 313.7K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.28.md
- The names of ResourceClaims generated from ResourceClaimTemplate are now generated. The base name is still `<pod>-<claim name>`, but a random suffix will avoid name collisions. ([#117351](https://github.com/kubernetes/kubernetes/pull/117351), [@pohly](https://github.com/pohly)) [SIG API Machinery, Apps, Auth,...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:34:59 UTC 2024 - 456.9K bytes - Viewed (0) -
docs/en/docs/release-notes.md
* Composite bodies' IDs are now based on path, not only on route name, as the auto-generated name uses the function names, that can be duplicated in different modules. * The same new ID generation applies to response models. * This also changes the generated title for those models. * Only composite bodies and response models are affected because those are generated dynamically, they don't have a module (a Python file).
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Fri Nov 01 11:25:57 UTC 2024 - 460.3K bytes - Viewed (0)