add docs for StorageVersionMigration v1alpha1 #43538
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
also include initContainers
Signed-off-by: Kevin Grigorenko <[email protected]>
Remove references to CrossNamespaceAffinity The scope CrossNamespaceAffinity does not exist. Attempting to feed the example YAML to `kubectl create` results in the following error: > The ResourceQuota "disable-cross-namespace-affinity" is invalid: > * spec.scopeSelector.matchExpressions.scopeName: Invalid value: > "CrossNamespaceAffinity": unsupported scope Add missing operator for CrossNamespacePodAffinity Trying to create the example ResourceQuotas without an operator results in the following error from `kubectl create`: > The ResourceQuota "disable-cross-namespace-affinity" is invalid: > * spec.scopeSelector.matchExpressions.operator: Invalid value: "": must be > 'Exist' when scope is any of ResourceQuotaScopeTerminating, > ResourceQuotaScopeNotTerminating, ResourceQuotaScopeBestEffort, > ResourceQuotaScopeNotBestEffort or > ResourceQuotaScopeCrossNamespacePodAffinity > * spec.scopeSelector.matchExpressions.operator: Invalid value: "": not a valid > selector operator The error message itself has another bug, as the operator is Exist*s*, not Exist. Signed-off-by: Simon Engmann <[email protected]>
We are talking about pods here, not about services yet.
Semantic fix
It is the ReplicaSet who recreates dead pods and not the deployment
Reorder sentence
incorporated review comments
secret is used to have authenticate with the private Container registry it should be in the same namespace which container the workloads Signed-off-by: Dipankar Das <[email protected]>
…te-registry.md Co-authored-by: Tim Bannister <[email protected]>
Co-authored-by: Rodolfo Martínez Vega <[email protected]>
Co-authored-by: Rodolfo Martínez Vega <[email protected]>
Gracias por esto! Co-authored-by: Rodolfo Martínez Vega <[email protected]>
Co-authored-by: Tim Bannister <[email protected]>
Update content/en/docs/tasks/administer-cluster/kubelet-config-file.md Co-authored-by: Qiming Teng <[email protected]>
As outlined in kubernetes/kubernetes#119941, the implementation is more specific than a regular glob match. Updating the docs to reflect that. Signed-off-by: Sascha Grunert <[email protected]>
…on/* Signed-off-by: xin.li <[email protected]>
Add doc-versions-list shortcode
* Add legacy-repos-deprecation shortcode and localization Signed-off-by: Marko Mudrinić <[email protected]> * Update install/upgrade guides to clarify that legacy repos are frozen Signed-off-by: Marko Mudrinić <[email protected]> * Update the legacy repos message Signed-off-by: Marko Mudrinić <[email protected]> --------- Signed-off-by: Marko Mudrinić <[email protected]>
…yKey works (#42780) * removes "tmpfs is cleared on node reboot" I believe the statement is confusing since we are in the emptyDir section of the documentation. If a Node is restarted then all pods that resided on that node will be rescheduled onto another Node. Rescheduled pods will have an empty volume whether you choose emptyDir.medium "Memory" or not. * removes bad comma * improves memory limit description Co-authored-by: Tim Bannister <[email protected]> * removes incorrect explanation for topologyKey in an affinity or anti-affinity rule (#1) The existing text does not make sense to me. There is no zone "V" or "R" in the example. I have changed the text to be consistent with top answer here which seems to make more sense: https://stackoverflow.com/questions/72240224/what-is-topologykey-in-pod-affinity * gives more context to node label configuration * manually wraps text and replaces absolute links with relative ones * Update assign-pod-node.md --------- Co-authored-by: Tim Bannister <[email protected]> Co-authored-by: Qiming Teng <[email protected]>
[zh-cn]sync kubelet-config-file inject-data-application/* manage-daemon/*
[zh] Sync /services-networking/service.md
[fr] fix: update deprecated command in code example
k8s-ci-robot
added
do-not-merge/work-in-progress
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
area/blog
k8s-ci-robot
added
language/es
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref: kubernetes/enhancements#4192
/sig api-machinery