Some Golang CVEs get flagged in the suc binary as it was built with an
older golang version. Use go 1.22.6
Updating other go module deps.
SLES update is required for libc compatiblity with latest ginkgo
version.
Update golangci-lint. Most gingko and gomega changes are to fix linting
failures.
Update sonobuoy
docker bridge address is added to tls-san to avoid cert errors when
using the client to connect the KUBEHOST.
Drop deprecated version field in the docker compose manifests.
It is recommended that the next release be v0.15.0 as 0.14.0 was already
published and deleted in the past and gosumdb already has entries.
* Make pkg/apis a go module
system-upgrade-controller depends on k8s.io/kubernetes which makes it very
difficult to include as a dependency from another project. The main reason
a project would want to have a go dependency on system-upgrade-controller
would be for the types. This makes the apis package a first class module
that one can depend on without having to depend on k8s.io/kubernetes
* Swith to vendorless
This is a decent-sized refactor, primarily in how the controller is setup, that I think enhances readability. Additionally, wrangler has been upgraded which now supports openapi schema creation so norman has been dropped.
Primarily, however, this change is meant to address #25 (and possibly #36) caused by a bug in wrangler that:
- prevented the controller from properly replacing jobs that could not be patched (pod tempalte spec changes)
- prevented the controller from replacing a job generated with the `apply.WithNoDelete` option
- prevented the controller from processing external plan edits in a timely manner (no more long waits due to spurious replace-wait errors)
Fixes#25Fixes#34
Depends on rancher/wrangler#66
- includes removal of controller serviceAccountName references and envvar
- image tarballs a la `docker save` are added to dist/artifacts
- sonobuoy plugin yaml added to dist/artifacts
- introduces e2e-tests tag suffix image that can be used for the sonobuoy plugin
- Add `secrets` references to **Plan** spec. Changes in referenced `secrets` can trigger re-application of a **Plans**.
- The label that a **Plan** places on an applied `node` is no longer the `status.latestVersion` but is instead a sha224 digest of `status.latestVersion` and the key-order-value(s) of each secret's `data` in the order each `secret` is specified. This value is represented as `status.latestHash`
Swastik Gour