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
MGMT-14923: add OSImageVersion to InfraEnvSpec #5365
MGMT-14923: add OSImageVersion to InfraEnvSpec #5365
Conversation
@danielerez: This pull request references MGMT-14923 which is a valid jira issue. In response to this:
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/test-infra repository. |
Skipping CI for Draft Pull Request. |
/test all |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielerez 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 |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5365 +/- ##
==========================================
+ Coverage 67.59% 67.66% +0.07%
==========================================
Files 226 226
Lines 33304 33349 +45
==========================================
+ Hits 22511 22567 +56
+ Misses 8759 8746 -13
- Partials 2034 2036 +2
|
529fce7
to
fbcb56a
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.
Can you also ensure there is a test for the case where the cluster is set?
Actually didn't find something specific for this flow, added. |
fbcb56a
to
48a8f5e
Compare
Looks good, any reason it's still in draft? |
Not really:) Moved to ready for review. |
@danielerez: This pull request references MGMT-14923 which is a valid jira issue. In response to this:
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/test-infra repository. |
f0a1e0d
to
61ec6da
Compare
Looks good to me, but I'll give @avishayt a chance to 👍 the API |
Introduced a new property to InfraEnvSpec: 'OSImageVersion'. The property can be used for creating an InfraEnv through kube-api with a specific OS image version. The 'OSImageVersion' is useful for HyperShift flows which use late binding, hence, the InfraEnv isn't created according to a cluster version (thus latest OS image is used as a fallback). Notes: * The specified version should refer to an OSImage from the list in AgentServiceConfig, otherwise the condition is set to failure. * When a ClusterRef is provided, we still use the cluster's version for creating the InfraEnv. Thus, The property should not be provided along with OSImageVersion to avoid a conflict (validated with a WebHook).
61ec6da
to
666022c
Compare
@danielerez: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
/lgtm |
36d3543
into
openshift:master
Introduced a new property to InfraEnvSpec: 'OSImageVersion'. The property can be used for creating an InfraEnv through kube-api with a specific OS image version. The 'OSImageVersion' is useful for HyperShift flows which use late binding, hence, the InfraEnv isn't created according to a cluster version (thus latest OS image is used as a fallback). Notes: * The specified version should refer to an OSImage from the list in AgentServiceConfig, otherwise the condition is set to failure. * When a ClusterRef is provided, we still use the cluster's version for creating the InfraEnv. Thus, The property should not be provided along with OSImageVersion to avoid a conflict (validated with a WebHook).
Introduced a new property to InfraEnvSpec: 'OSImageVersion'. The property can be used for creating an InfraEnv through kube-api with a specific OS image version. The 'OSImageVersion' is useful for HyperShift flows which use late binding, hence, the InfraEnv isn't created according to a cluster version (thus latest OS image is used as a fallback). Notes: * The specified version should refer to an OSImage from the list in AgentServiceConfig, otherwise the condition is set to failure. * When a ClusterRef is provided, we still use the cluster's version for creating the InfraEnv. Thus, The property should not be provided along with OSImageVersion to avoid a conflict (validated with a WebHook).
Introduced a new property to InfraEnvSpec: 'OSImageVersion'. The property can be used for creating an InfraEnv through kube-api with a specific OS image version. The 'OSImageVersion' is useful for HyperShift flows which use late binding, hence, the InfraEnv isn't created according to a cluster version (thus latest OS image is used as a fallback). Notes: * The specified version should refer to an OSImage from the list in AgentServiceConfig, otherwise the condition is set to failure. * When a ClusterRef is provided, we still use the cluster's version for creating the InfraEnv. Thus, The property should not be provided along with OSImageVersion to avoid a conflict (validated with a WebHook).
Introduced a new property to InfraEnvSpec:
OSImageVersion
.The property can be used for creating an InfraEnv through kube-api with a specific OS image version.
The
OSImageVersion
is useful for HyperShift flows which use late binding, hence, the InfraEnv isn't created according to a cluster version (thus, the latest OS image is used as a fallback).Notes:
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist