Node Resource Interface (NRI) is a common framework for plugging
domain or vendor-specific custom logic into container runtime like
containerd. This commit introduces a new congiguration field
`containerd.nri`, providing cluster admins the flexibility to opt
in for this feature in containerd and tune some of its parameters.
By default, NRI is disabled here in accordance with the containerd's
default config file.
Signed-off-by: Feruzjon Muyassarov <feruzjon.muyassarov@intel.com>
* tasks dependencies
* FindAddresses should proceed even if LBID is empty
* refacto instance: handle several instances in IG + volumeSize in model
* refacto lb_backend: set servers' IPs in backend task rather than instance
* dns changes for tf support
* render Scaleway s3 objects + add zone to outputs
* add terraform support to documentation
* new instance unique name should be given according to actual instances names
* avoid untimely changes in tf + tag instance IPs to avoid orphaned IPs at cluster deletion
* update integration tests
* review comments
* add IPs to the resources to be deleted with the cluster
* add task + model for DNS record
* OpenStack: add server group name override annotation
* use retries to listinstances
* add support for multiple clusters in same tenant
* run hack-expected.sh
* add test for serverGroupName annotation
* use retry
- there is a separate `coredns-autoscaler` that is spun up in more recent kOps versions
- so the `kube-dns-autoscaler` is no longer needed after an upgrade to CoreDNS
- and possibly could conflict if they both targeted the same deployment
- updating the `kube-dns-autoscaler` was the most confusing part, so this simplifies things a good bit!
- links still worked before, but some were as old as Cilium v1.6, so update to newest proactively
- also makes it consistent / easier for readers when all of the links go to the same version of the docs
* feat(karpenter): Upgrade to version 0.27.0
Upgrade Karpenter to current last stable version `0.27.0`.
Template have been updated to use the same templates than the Helm chart.
* feat(karpenter): Use AWSNodeTemplate for launchTemplate
To set Launch Templates is deprecated into the provisioner, it is recommends using the `AWSNodeTemplate` to set it.
Ref:
- https://karpenter.sh/v0.27.0/concepts/node-templates/
* feat(karpenter): Enable pruning addon
* Use extra flags in upgrade-ab scenario test
* feat(karpenter): Drop `karpenter` feature flag
* feat(karpenter): Add release note for `1.27`
* feat(karpenter): Upgrade to version 0.27.3
* feat(karpenter): fix template
* feat(karpenter): Upgrade to version 0.27.5
* Update Karpenter documentation with depending kops version
* Delete KOPS_FEATURE_FLAGS from e2e test `run-test`
* Run hack/update-expected.sh