-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add warning notes if helm charts Istio version is already EOL #1294
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: zufardhiyaulhaq <[email protected]>
cc @howardjohn |
Signed-off-by: zufardhiyaulhaq <[email protected]>
@@ -160,6 +163,9 @@ type Manifest struct { | |||
Dependencies IstioDependencies `json:"dependencies"` | |||
// Version specifies what version of Istio this release is | |||
Version string `json:"version"` | |||
// EOLDate specifies what is the date when this Istio version become EOL | |||
// Should be in format "yyyy-mm" | |||
EOLDate string `json:"eolDate"` |
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.
If we already have to update istioctl binary directly it seems like we could just update the helm notes directly as well? We can have a test to check they are in sync if needed
Will defer to @ericvn
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.
do you mean to update the helm notes directly on istio/istio repository?
Signed-off-by: zufardhiyaulhaq <[email protected]>
@ericvn can you help here? |
cc @istio/wg-test-and-release-maintainers please help review |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: zufardhiyaulhaq [email protected]
fix istio/istio#41747, introduce a warning if the current date is near or after EOL of the date defined in the release builder.