modules/ignition: introduce runtime-mappings.yaml#2039
Conversation
29e8234 to
f7f4004
Compare
f7f4004 to
d6f0188
Compare
|
run smokes |
|
@robszumski this is the secondary source of version-mappings for the bootstrapper. The primary source is at https://github.com/coreos-inc/tectonic-cluo-operator/pull/13. Both of them will need to be owned by somebody involved in the release process and sync'd. /cc @Quentin-M @diegs |
|
Bikeshedding question: is the name specific enough? This thing used to be called |
d6f0188 to
9f15f65
Compare
|
Can one of the admins verify this patch? |
|
cc @derekparker |
|
One thing we have discussed offline is using this configmap to express both Docker and Kubelet versions, since those are so tightly coupled. This means that the KVO Node Agent will also read from this configmap, and KVO will write to this configmap with the versions of docker / kubelet that are defined in the KVO upgrade spec. The upgrade flow for Nodes then becomes:
|
|
The proposed flow makes sense - it's definitely an improvement - but I'm not sure that it's necessary, given that most kubelet upgrades will be non-disruptive and not involve tectonic-torcx. |
| 1.8: | ||
| # As per k8s issue 42926, 1.11, 1.12, 1.13, and 17.03 are supported | ||
| # see https://github.com/kubernetes/kubernetes/issues/42926#issuecomment-325733231 | ||
| docker: [ "1.13", "1.12"] |
There was a problem hiding this comment.
We don't ship 1.13. We should instead just jump straight to 17.03.
There was a problem hiding this comment.
This was just an optimistic forecast made at 1.7 time. This file is not yet consumed by the bootstrapper anyway, so I'm keeping this in sync with the old one for the moment, will bump them all at the same time once testing is green. We'll also need a forecast for 1.9.
|
@diegs so it looks like this can be already merged as is? (I'll decouple and take care of the new version followup) |
|
We did some changes (#2082) to the testing process. Please rebase on to current master, so that the |
May I understand why/how? |
|
@Quentin-M he means that this needs to be sync'd with one that is shipped in the KVO or TCLUO |
2b58dc8 to
0a2c0b2
Compare
| @@ -1,25 +0,0 @@ | |||
| # This file is supposed to be symlinked in consuming modules | |||
|
Rebased, PTAL. It is ready for review and targeted at Helium as per https://github.com/coreos-inc/kube-version-operator/blob/master/Documentation/tectonic_torcx.md#tectonic-install-flow. I think this needs additional labels in order to be tested on all platforms. |
|
ok to test |
| tectonic_prometheus_operator = "quay.io/coreos/tectonic-prometheus-operator:v1.7.1" | ||
| tectonic_cluo_operator = "quay.io/coreos/tectonic-cluo-operator:v0.2.4" | ||
| tectonic_torcx = "quay.io/coreos/tectonic-torcx:installer-latest" | ||
| tectonic_torcx = "quay.io/coreos/tectonic-torcx:v0.2.0" |
There was a problem hiding this comment.
@s-urbaniak @sym3tri this gets rid of the mutable tag.
0a2c0b2 to
f0e972f
Compare
|
@cpanato What is the ETA on these tests passing? |
f0e972f to
6f36d18
Compare
|
@meghnagala I'm re-spawning my local metal cluster to double-check I didn't miss anything obvious. I've also re-pushed this PR, re-kicking the CI to ensure I didn't hit some odd flakes. If neither of those helps, I'm going to grab @cpanato tomorrow morning to dig further. |
|
@lucab looks like all tests failed due timeout during the bootstrap process, we have all the logs from docker and journals we can dig into tomorrow if you don't mind. |
6f36d18 to
fc770dd
Compare
This introduces a runtime-mappings.yaml to be used by tectonic-torcx. In particular, this file is consumed by k8s-node-bootstrap.service as a fallback to determine the docker version to install when the api-server is unreachable (e.g. while installing a brand new cluster). If an api-server is available, an up-to-date version of this data will be sourced from a config-map instead as a primary source.
fc770dd to
4772a76
Compare
|
This is still failing due to an unrelated failure in metal testing environment. We tracked this down to broken bridge connectivity across VMs on the Packet machine, which should be hopefully resolved soon. I'm going to rebase and push this once metal testing environment is fixed. |
|
ok to test |
|
Some azure tests failed; running those selectively so we can run just the bare-metal tests once that CI infrastructure is fixed. |
|
retest this please |
|
now all azure are green |
|
retest this please |
|
@lucab tests passed |
squat
left a comment
There was a problem hiding this comment.
PR was already LGTM'd. reapproving so we can merge.
This introduces a runtime-mappings.yaml to be used by tectonic-torcx.
In particular, this file is consumed by k8s-node-bootstrap.service
as a fallback to determine the docker version to install when the
api-server is unreachable (e.g. while installing a brand new cluster).
If an api-server is available, an up-to-date version of this data
will be sourced from a config-map instead as a primary source.
Part of OST-79
/cc @squeed