Some time ago, an EKS cluster was attached to be managed with NKP (Fleet Management). Now, a Platform Engineer has been asked to disconnect the EKS cluster from NKP for licensing reasons. After disconnecting the cluster, the developers realized that application changes are still being reflected in the EKS cluster, despite the fact that the EKS cluster was successfully detached from NKP. How should the engineer resolve this issue?

Question

Accepted Answer

D. Detached cluster's Flux installation must be manually disconnected from the management Git

Answer

A. Forcefully detach EKS cluster: nkp detach cluster -c detached-cluster-name --force

Answer

B. Detached cluster must also be deleted from NKP: nkp delete cluster -c detached-cluster-name

Answer

C. Developers must have some bad configuration in the deployment config files. Ask for revision or

Some time ago, an EKS cluster was attached to be managed with NKP (Fleet Management). Now, a Platform Engineer has been asked to disconnect the EKS cluster from NKP for licensing reasons. After…

Question

Options

How the community answered

Explanation

Topics

Community Discussion