- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 19 for Initialize (0.11 sec)
-
docs/en/docs/release-notes.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Fri Nov 01 11:25:57 UTC 2024 - 460.3K bytes - Viewed (0) -
doc/go_spec.html
Multiple variables on the left-hand side of a variable declaration initialized by single (multi-valued) expression on the right-hand side are initialized together: If any of the variables on the left-hand side is initialized, all those variables are initialized in the same step. </p> <pre> var x = a var a, b = f() // a and b are initialized together, before x is initialized </pre> <p>
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Wed Oct 02 00:58:01 UTC 2024 - 282.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.6.md
### Federation * The --dns-provider argument of 'kubefed init' is now mandatory and does not default to `google-clouddns`. To initialize a Federation control plane with Google Cloud DNS, use the following invocation: 'kubefed init --dns-provider=google-clouddns' ([#42092](https://github.com/kubernetes/kubernetes/pull/42092), [@marun](https://github.com/marun))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Dec 24 02:28:26 UTC 2020 - 304K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
- Updated google.golang.org/protobuf to `v1.33.0` to resolve `CVE-2024-24786`. ([#123758](https://g...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:40:14 UTC 2024 - 309.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.7.md
* Support kube-master-url flag without kubeconfig * Fix concurrent R/Ws in dns.go * Fix confusing logging when initialize server * Fix printf in cmd/kube-dns/app/server.go * Fix version on startup and `--version` flag * Support specifying port number for nameserver in stubDomains #### kube-proxy
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 308.7K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.29.md
- `kubelet` , when using `--cloud-provider=external`, will now initialize the node addresses with the value of `--node-ip` , if it exists, or waits for the cloud provider to assign the addresses. ([#121028](https://github.com/kubernetes/kubernetes/pull/121028), [@aojea](https://github.com/aojea))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:37:31 UTC 2024 - 375.1K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.18.md
## Changelog since v1.18.2 ## Changes by Kind ### Bug or Regression - An issue preventing GCP cloud-controller-manager running out-of-cluster to initialize new Nodes is now fixed. ([#90057](https://github.com/kubernetes/kubernetes/pull/90057), [@ialidzhikov](https://github.com/ialidzhikov)) [SIG Apps and Cloud Provider]
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
* Object quotas are not consistently charged or updated. Specifically, the object count quota does not reliably account for uninitialized objects. Some quotas are charged only when an object is initialized. Others are charged when an object is created, whether it is initialized or not. We plan to fix this issue in a future release. For more information, see [#53109](https://github.com/kubernetes/kubernetes/issues/53109). ## Deprecations
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.15.md
- The cloud config for Azure cloud provider can now be initialized from Kubernetes secret azure-cloud-provider in kube-system namespace - the secret is a serialized version of `azure.json` file with key cloud-config. And the secret name is azure-cloud-provider.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu May 05 13:44:43 UTC 2022 - 278.9K bytes - Viewed (0) -
common-protos/k8s.io/api/core/v1/generated.proto
// More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes // +optional optional Probe readinessProbe = 11; // StartupProbe indicates that the Pod has successfully initialized. // If specified, no other probes are executed until this completes successfully. // If this probe fails, the Pod will be restarted, just as if the livenessProbe failed.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 255.8K bytes - Viewed (0)