Applications - Test Release 2.26

[ahmedwaleedmalik]

We need to test Applications thoroughly because of the various issues that we are encountering recently.

• [ ] Initial applications are working
• [ ] Applications created after cluster creation have the correct namespace, values, and are properly installed
• [ ] Default applications are installed for new clusters
• [ ] Enforced applications are installed for all cluster, updating applicationDefinition updates the applicationInstallation for all clusters
• [ ] Enforced/Default application with datacenter selector
• [ ] Deletion of applications works fine and namespaces are also cleaned up
• [ ] Not sure what other scenarios can be tested...

These tickets/PRs also need to be tested:

• https://github.com/kubermatic/kubermatic/issues/13742
• https://github.com/kubermatic/kubermatic/pull/13746
• https://github.com/kubermatic/kubermatic/pull/13743
• https://github.com/kubermatic/kubermatic/pull/13741
• https://github.com/kubermatic/kubermatic/pull/13121

For dashboard we tested the defaulting/enforcement functionality with https://github.com/kubermatic/dashboard/issues/6788

/milestone KKP 2.26

[ahmedwaleedmalik]

cc @csengerszabo someone needs to pick this and rest of the testing tickets as well

[ahmedwaleedmalik]

Would be nice if we can wait for https://github.com/kubermatic/kubermatic/pull/13746 before starting this ticket. Since those changes should also be tested against this ticket as already mentioned in the ticket description.

[ahmedwaleedmalik]

/label priority/high

[kubermatic-bot]

@ahmedwaleedmalik: The label(s) /label priority/high cannot be applied. These labels are supported: blocked by backend, merge-type/merge, merge-type/rebase, needs details, service accounts, Epic, MVP, customer-request, design, feature, proposal, ready-to-challenge, redesign, sig/api, sig/app-management, sig/cluster-management, sig/community, sig/infra, sig/networking, sig/ui, sig/virtualization, sprint, team/marketing, team/ps, lifecycle/frozen, backport-needed, backport-complete, ee, needs-release-testing, test/require-vsphere, test/require-kubevirt, test/require-vmwareclouddirector, test/require-nutanix. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/kubermatic/kubermatic/issues/13745#issuecomment-2363363468): >/label priority/high Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[xmudrii]

/priority high

[cnvergence]

hi @ahmedwaleedmalik, I will also add this one https://github.com/kubermatic/kubermatic/pull/13121