Add SNO upgrade workflows#17519
Conversation
00a9e85 to
e08062d
Compare
|
Reference: https://issues.redhat.com/browse/OTA-379 |
|
/retest |
1 similar comment
|
/retest |
a02a353 to
65334bd
Compare
18374fe to
3b75f9e
Compare
d8c53d8 to
bdf5630
Compare
|
/hold I'll create a new PR to fix |
There was a problem hiding this comment.
we called in single-node everywhere (rather than sno)
There was a problem hiding this comment.
is loki is something specific here? Just so i understand, or this is the standard flow
There was a problem hiding this comment.
Copied from regular upgrade workflow
There was a problem hiding this comment.
This step would setup promtail on the cluster, sending container and journald logs to the central repo, which can be queried by Grafana.
This is a standard practice for upgrade workflows, as intermediate containers can be lost during reboot (or the node may never come back)
|
Lets add those jobs here as well: https://testgrid.k8s.io/redhat-single-node |
This setups SNO cluster on AWS from `release:initial` and upgrades it to `release:latest`. Disruption tests are skipped, as they are not expected to pass in SNO configuration. As a test this adds periodic job to be testing 4.8 CI images every 24 hours
This test suite won't run disruption tests
| set -o nounset | ||
| set -o pipefail | ||
|
|
||
| SINGLE_NODE_AZURE_INSTANCE_TYPE="Standard_D32s_v3" |
There was a problem hiding this comment.
I expect there to be one set of folks maintaining these single-node conf step(s), so it might we worth a single single-node/conf command instead of the platform-specific sub-steps. On the other hand, I'm not in the maintainer set, so doesn't matter for me ;).
wking
left a comment
There was a problem hiding this comment.
Looks pretty good to me. Remaining wrinkles can be ironed out in follow-up work.
/lgtm
/retest
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hongkailiu, omertuc, vrutkovs, wking 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 |
|
@vrutkovs: 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. |
|
/hold cancel All issues were resolved |
|
@vrutkovs: Updated the following 3 configmaps:
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 kubernetes/test-infra repository. |
This setups SNO cluster on AWS and Azure from
release:initialand upgrades itto
release:latest. Disruption tests are skipped, as they are notexpected to pass in SNO configuration.
Split out from #16290 to speed up review.
TODO:
storageoperator on AWS - https://bugzilla.redhat.com/show_bug.cgi?id=1947402