AGENT-857: Agent day2 use clusterinfo#8009
AGENT-857: Agent day2 use clusterinfo#8009openshift-merge-bot[bot] merged 19 commits intoopenshift:masterfrom
Conversation
|
@andfasano: This pull request references AGENT-857 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
61765f2 to
d6e5b2b
Compare
6cfa3c5 to
ebc9aa3
Compare
8b9ea4e to
c8c31ce
Compare
|
@andfasano: This pull request references AGENT-857 which is a valid jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
99488f4 to
b561aba
Compare
|
/test e2e-aws-ovn-edge-zones-manifest-validation |
rwsu
left a comment
There was a problem hiding this comment.
Small spelling issue.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rwsu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cb42b4a to
0f029ff
Compare
These fake clients will be used to unit test ClusterInfo
0f029ff to
6912900
Compare
|
@andfasano: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
| ImageDigestSources []types.ImageDigestSource | ||
| DeprecatedImageContentSources []types.ImageContentSource | ||
| PlatformType hiveext.PlatformType | ||
| SSHKey string |
There was a problem hiding this comment.
Do you need to add InstallConfig fields like CPUPartitioning,FIPS, or any of the Networking fields?
There was a problem hiding this comment.
That's a good question @bfournie. @zaneb @rwsu @pawanpinjarkar what are your thoughts about it? I'd say that in this first iteration we could try to address just the min fields required, and eventually add them later in successive iterations
There was a problem hiding this comment.
OK, with the caveat that we can't get beyond Dev Preview without this stuff.
There was a problem hiding this comment.
There was a problem hiding this comment.
@bfournie from a first pass it looks like the mentioned settings are cluster dependent, so anything that could be set directly on the node. During the joining process I'd expect the fetched ignition would contain any necessary bits, I will verify for the case of FIPS for example.
|
Looks reasonable to me, just one question which may be covered in follow-on. |
| namespace: cluster0 | ||
| spec: | ||
| cpuArchitecture: x86_64 | ||
| ipxeScriptType: "" |
There was a problem hiding this comment.
The usage of ipxeScriptType is unclear to me. The only possible values in assisted are DiscoveryImageAlways and BootOrderControl. How is the agent installer using these values?
There was a problem hiding this comment.
I re-checked, and the test changes were triggered by the refactoring/changes in infraenv.go
|
/retest-required |
|
/lgtm |
This patch follows #7997, and starts injecting the
ClusterInfointo the agent assets graph. Mainly, the various assets - depending on the current workflow set - will grab the required inputs either from theOptionalInstallConfigorClusterInfoassets.So, this patch prepares the ground properly to allow modifying the
Ignitionasset in a subsequent PR.