addon

[miklezzzz]

Description

Why do we need it, and what problem does it solve?

Why do we need it in the patch release (if we do)?

What is the expected result?

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: <kebab-case of a module name> | <1st level dir in the repo>
type: fix | feature | chore
summary: <ONE-LINE of what effectively changes for a user>
impact: <what to expect for users, possibly MULTI-LINE>, required if impact_level is high ↓
impact_level: default | high | low

[deckhouse-BOaTswain]

🔴 e2e: AWS for deckhouse:addon-scheduler failed in 1h21m12s.

E2e for aws WithoutNAT;containerd;1.25 was failed. Use:
ssh -i ~/.ssh/e2e-id-rsa centos@18.159.28.202 - connect for debugging;

/e2e/abort aws;WithoutNAT;containerd;1.25 9219718099 9219718099-1-con-1-25 /sys/deckhouse-oss/install:pr8285 centos@18.159.28.202 - for abort failed cluster

Workflow details (1 job failed)

AWS-WithoutNAT-Containerd-1.25 - Connection string: ssh centos@18.159.28.202

🔴 e2e: AWS, Containerd, Kubernetes 1.25 failed in 1h20m27s.

[miklezzzz]

/e2e/abort aws;WithoutNAT;containerd;1.25 9219718099 9219718099-1-con-1-25 /sys/deckhouse-oss/install:pr8285 centos@18.159.28.202

[deckhouse-BOaTswain]

🔴 destroy cluster: AWS for refs/heads/main failed in 32s.

Workflow details (1 job failed)

🔴 destroy cluster: AWS, Containerd, Kubernetes 1.25 failed in 8s.

[miklezzzz]

/e2e/abort aws;WithoutNAT;containerd;1.25 9219718099 9219718099-1-con-1-25 /sys/deckhouse-oss/install:pr8285 centos@18.159.28.202

[deckhouse-BOaTswain]

🔴 destroy cluster: AWS for refs/heads/main failed in 34s.

Workflow details (1 job failed)

🔴 destroy cluster: AWS, Containerd, Kubernetes 1.25 failed in 8s.