-
Notifications
You must be signed in to change notification settings - Fork 40.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actually support service publishNotReadyAddresses
#63742
Actually support service publishNotReadyAddresses
#63742
Conversation
f60f11c
to
db306e4
Compare
/retest |
This was added and the annotation was deprecated, but it was never implemented.
db306e4
to
c038f60
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surprised that this is not implemented..
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrHohn, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cc @kow3ns |
Automatic merge from submit-queue (batch tested with PRs 63792, 63495, 63742, 63332, 63779). If you want to cherry-pick this change to another branch, please follow the instructions here. |
The reason this hadn't been implemented yet was explained in #61056 (comment) With that said, I talked to @kow3ns after that comment and he seemed willing to consider this type of implementation, at least as an intermediate step. |
This fixes the Redis StatefulSet e2e test by adding the missing `publishNotReadyAddresses: true` field, which was accidentially left out in kubernetes#63742. Without this fix, the redis e2e test will fail because the pod is unable to lookup the service: ``` 2018/09/14 13:57:10 lookup redis on 172.31.9.247:53: no such host ``` Signed-off-by: Mikkel Oscar Lyderik Larsen <[email protected]>
This fixes the Redis StatefulSet e2e test by adding the missing `publishNotReadyAddresses: true` field, which was accidentially left out in kubernetes#63742. Without this fix, the redis e2e test will fail because the pod is unable to lookup the service: ``` 2018/09/14 13:57:10 lookup redis on 172.31.9.247:53: no such host ``` Signed-off-by: Mikkel Oscar Lyderik Larsen <[email protected]>
This annotation has been deprecated since Kuberneets 1.8 and the publishNotReadyAddresses parameter replacing it has been correctly implemented in Kubernetes 1.11 (see kubernetes/kubernetes#63742)
This annotation has been deprecated since Kuberneets 1.8 and the publishNotReadyAddresses parameter replacing it has been correctly implemented in Kubernetes 1.11 (see kubernetes/kubernetes#63742)
https://jira.percona.com/browse/K8SPXC-876 "service.alpha.kubernetes.io/tolerate-unready-endpoints" annotation has been deprecated since Kuberneets 1.8 and the spec.publishNotReadyAddresses parameter replacing it has been correctly implemented in Kubernetes 1.11 (see kubernetes/kubernetes#63742)
https://jira.percona.com/browse/K8SPXC-876 "service.alpha.kubernetes.io/tolerate-unready-endpoints" annotation has been deprecated since Kuberneets 1.8 and the spec.publishNotReadyAddresses parameter replacing it has been correctly implemented in Kubernetes 1.11 (see kubernetes/kubernetes#63742)
The annotation `service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"` is deprecated since Kubernetes 1.11, following kubernetes/kubernetes#63742 The template input both fields, the annotation and the substituted field `.spec.publishNotReadyAddresses=True` but it becomes incompatible with Kubernetes <=1.10 so a check Kubernetes version resolve it put the right fields based on Kubernetes version.
* fix: publishNotReadyAddresses K8s version check The annotation `service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"` is deprecated since Kubernetes 1.11, following kubernetes/kubernetes#63742 The template input both fields, the annotation and the substituted field `.spec.publishNotReadyAddresses=True` but it becomes incompatible with Kubernetes <=1.10 so a check Kubernetes version resolve it put the right fields based on Kubernetes version. * Bumping chart version * Update Chart.yaml --------- Co-authored-by: Aaron Layfield <[email protected]>
* This annotation has been deprecated since Kuberneets 1.8 and the publishNotReadyAddresses parameter replacing it has been correctly implemented in Kubernetes 1.11 (see kubernetes/kubernetes#63742) * See also: hashicorp#363
This was added and the annotation was deprecated, but it was never
implemented.
xref #63741
Release note: