https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
It looks to be already installed?
p
Yes. This might be this scenario.
The scenario is Pulumi will add this label, app.kubernetes.io/managed-by, with the value as “pulumi” automatically. However it conflict with the eks addon, so it will fail with conflict error message when I tried to create the addon via pulumi.
Do you have any idea about it?
b
if the app is already installed in your cluster, you need to remove it or import it into state instread of trying to reinstall it
p
Got it. How to import it into state?
b
p
Thanks
One more question is how I can check the return error, if the error is because of the resource is existing I can skip this error
b
You cannot, the kubernetes api is returning the error
p
Hi Jaxxstorm, Tried to create ebs-csi-controller-sa before aws-ebs-csi-driver add-on. I got this conflict error, “ServiceAccount ebs-csi-controller-sa - .metadata.labels.app.kubernetes.io/managed-by”. Do you have any suggestion? Thanks
b
does a service account with that name already exist?
p
No. I created it first, for I need to annotate the role data on it for the addon
I mean the sa was created by my pulumi code before the addon
Got this error when I tried to import sa into pulumi.
Copy code
kubernetes:core/v1:ServiceAccount (ebs-csi-node-sa):
    error: inputs to import do not match the existing resource
Could you please give me some ideas. thanks
b
the error is fairly self explanatory
p
My question is what is the unmatched data and how I can fix it. I guess that is the labels. I tried to use “IgnoreChanges” to ignore these unmatched data, but I failed. My code is like this:
Copy code
pulumi.IgnoreChanges([]string{"metadata.labels.*", "metadata.annotations.*"}))
Is the syntax right? Thanks a lot.
Copy code
awsEbsCsiDriversa, err := corev1.NewServiceAccount(ctx, fmt.Sprintf("%s", _AwsEbsCsiDriverSaName), &corev1.ServiceAccountArgs{
			Metadata: &metav1.ObjectMetaArgs{
				ClusterName: eksCluster.Core.Cluster().Name(),
				Name:        pulumi.String(_AwsEbsCsiDriverSaName),
				Namespace:   pulumi.String(_KubeSystemNameSpaceName),
			},
		},
			pulumi.Provider(k8sProviderEnabledServerSideApply),
			pulumi.DependsOn([]pulumi.Resource{iamRole4AwsEbsCsiDriver}),
			pulumi.Import(pulumi.ID(fmt.Sprintf("%s/%s", _KubeSystemNameSpaceName, _AwsEbsCsiDriverSaName))),
			pulumi.Protect(true),
			pulumi.IgnoreChanges([]string{"metadata.labels.*", "metadata.annotations.*"}))
		if err != nil {
			return fmt.Errorf("error creating service account: %v", err)
		}
This is my code. I didn’t set labels here.
Copy code
apiVersion: v1
kind: ServiceAccount
metadata:
  creationTimestamp: "2023-01-09T10:29:51Z"
  labels:
    <http://app.kubernetes.io/component|app.kubernetes.io/component>: csi-driver
    <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: EKS
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: aws-ebs-csi-driver
    <http://app.kubernetes.io/version|app.kubernetes.io/version>: 1.14.0
  name: ebs-csi-controller-sa
  namespace: kube-system
  resourceVersion: "4479"
  uid: bc03278e-8591-47d9-a224-675a7f6f9000
This is the SA in kubernetes
b
You can’t 
ignoreChanges
on an import, the inputs have to match. You’ll need to add the labels to your metadata
p
Got it. Thanks.
3 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by