miniature-leather-70472
04/23/2021, 3:53 PMbillowy-army-68599
colossal-twilight-92354
04/23/2021, 6:34 PMpulumi import <kubernetes:helm.sh/v3:Chart> mychartname mychartname
, but keep getting error: Preview failed: resource 'mychartname' does not exist
(despite being able to successfully import k8s resources independent from importing the chart itssself). How do others handle importing chart state?proud-pizza-80589
04/24/2021, 8:06 AMsticky-hydrogen-53391
04/24/2021, 8:22 AMproud-pizza-80589
04/26/2021, 3:48 PMpurple-plumber-90981
04/28/2021, 6:58 AM<https://www.pulumi.com/blog/infrastructure-as-code-resource-naming/>
??
my_namespace = k8s.core.v1.Namespace("mynamespace")
gets me a namespace called mynamespace-778h547k when i really just want “mynamespace”kind-mechanic-53546
04/28/2021, 7:00 AM... { metadata: { name: yournamehere,...
purple-plumber-90981
04/28/2021, 7:02 AMeks_cluster = aws.eks.Cluster("my-eks-cluster", opts=eks_opts, **eks_cluster_config)
how would i achieve a cluster called “my-eks-cluster” rather than “my-eks-cluster-3ef8ab7” ?kind-mechanic-53546
04/28/2021, 7:04 AMkind-mechanic-53546
04/28/2021, 7:05 AMicy-jordan-58549
04/28/2021, 3:04 PMCustomResourceDefinition "<http://kafkas.kafka.strimzi.io|kafkas.kafka.strimzi.io>" is invalid: metadata.annotations: Too long: must have at most 262144 bytes
purple-plumber-90981
04/29/2021, 6:33 AMmany-psychiatrist-74327
04/30/2021, 9:56 PMk8s.yaml.ConfigFile
purple-plumber-90981
05/03/2021, 9:08 PMaws eks --region us-east-1 update-kubeconfig
and pulumi config set kubernetes:context
outside of the stackcolossal-australia-65039
05/03/2021, 9:35 PMpulumi preview --diff
nor pulumi up
shows the detailed diff for my deployments. For example, when my actual diff is an image change all I see is:
~ kubernetes:apps/v1:Deployment: (update)
~ spec: {
~ template: {
~ spec: {
~ containers: [
~ [0]: {
}
]
}
}
}
I'm on version 3.1.0 for pulumi, and my npm libs are
"@pulumi/kubernetes": "^3.0.0",
"@pulumi/pulumi": "^3.0.0",
this happened before the 3.0 upgrade but i only decided to ask about it now. Anyone know what's going on and how to fix it?lemon-monkey-228
05/04/2021, 2:30 PMlemon-monkey-228
05/04/2021, 2:31 PMlemon-monkey-228
05/04/2021, 2:31 PMpulumi stack export
then removing the resource into a pulumi stack import
caused the create
message to appear on the stack preview, but it didn’t actually happenpurple-plumber-90981
05/05/2021, 2:32 AM# setup EFS CSI driver
k8s_k_efscsi = k8s.kustomize.Directory(
"itplat-kust-efs-driver",
directory="<https://github.com/kubernetes-sigs/aws-efs-csi-driver/deploy/kubernetes/overlays/stable/ecr/?ref=release-1.1>",
resource_prefix="itplat-kust-efs-driver",
opts=pulumi.ResourceOptions(provider=k8s_use1_provider),
)
works fine the first time but every subsequent pulumi up
i get
Diagnostics:
pulumi:pulumi:Stack (aws_eks-itplat-aws-eks):
error: update failed
<kubernetes:storage.k8s.io/v1beta1:CSIDriver> (<http://itplat-kust-efs-driver-efs.csi.aws.com|itplat-kust-efs-driver-efs.csi.aws.com>):
warning: This resource contains Helm hooks that are not currently supported by Pulumi. The resource will be created, but any hooks will not be executed. Hooks support is tracked at <https://github.com/pulumi/pulumi-kubernetes/issues/555>
warning: <http://storage.k8s.io/v1beta1/CSIDriver|storage.k8s.io/v1beta1/CSIDriver> is deprecated by <http://storage.k8s.io/v1/CSIDriver|storage.k8s.io/v1/CSIDriver>.
error: resource <http://efs.csi.aws.com|efs.csi.aws.com> was not successfully created by the Kubernetes API server : <http://csidrivers.storage.k8s.io|csidrivers.storage.k8s.io> "<http://efs.csi.aws.com|efs.csi.aws.com>" already exists
agreeable-ram-97887
05/05/2021, 10:49 AMDuplicate resource URN 'urn:pulumi:prod::submission_strategy::<kubernetes:helm.sh/v3:Chart$kubernetes:apiregistration.k8s.io/v1:APIService::v1beta1.metrics.k8s.io>'; try giving it a unique name
Note that I am already using the resource_prefix
argument in my “ChartOpts” object to separate the resources URI’s for each cluster, and except for the one “APIService” resource this appears to work as expected.
Looking into the docs, I don’t see a clear way to specify the “APIService” resource URN 😕. Anyone have any suggestions ?lemon-monkey-228
05/05/2021, 12:11 PMk8s.core.v1.Secrets.get
as an example but get my hand slapped by Pulumi when it runs in an update.
/* Returns auth from a `ServiceAccount`'s associated secret */
export const getServiceAccountAuth = (serviceAccount: ServiceAccount): pulumi.Output<{ token: string, caCert: string}> =>
pulumi.output(serviceAccount.secrets[0].name).apply(secretName => {
const secret = k8s.core.v1.Secret.get(secretName, secretName)
const { token, ['ca.crt']: caCert } = secret.data.get()
return { token, caCert }
})
lemon-monkey-228
05/05/2021, 12:12 PMpurple-plumber-90981
05/06/2021, 5:31 AM<https://www.pulumi.com/docs/reference/pkg/kubernetes/yaml/configfile/>
it describes the option of Using a literal string containing YAML, or a list of such strings:
and i was expecting a k8s.ConfigFile(“myconfig”, config=“”"<inline yaml>“”") but cant see anything like that, only file=
bumpy-summer-9075
05/06/2021, 3:20 PMdata
of a configMap and it wants to delete-replace the configMap, and the deployment that refers to it, causing downtime.
--kubernetes:core/v1:ConfigMap: (delete-replaced)
[id=default/project-internal-tools-service-common]
[urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
[provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
+-kubernetes:core/v1:ConfigMap: (replace)
[id=default/project-internal-tools-service-common]
[urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
[provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
~ data: {
+ FOO: "bar"
}
++kubernetes:core/v1:ConfigMap: (create-replacement)
[id=default/project-internal-tools-service-common]
[urn=urn:pulumi:internal-tools.dev::project-internal-tools::kubernetes:core/v1:ConfigMap::common]
[provider=urn:pulumi:internal-tools.dev::project-internal-tools::pulumi:providers:kubernetes::eks::...]
~ data: {
+ FOO: "bar"
}
(this configMap was not initially created by Pulumi, it was imported)billowy-army-68599
witty-vegetable-61961
05/06/2021, 9:40 PMfaint-dog-16036
05/07/2021, 1:54 PMingress-nginx
? I'd prefer not to rely on helm, as it adds another layer of complexity that I'm trying to avoid, but using kube2pulumi
on ingress backend yml feels fairly clunky.colossal-australia-65039
05/07/2021, 8:53 PMcert-manager/cert-manager-cainjector
resource has been creating...
for several minutes already. Why isn't it essentially instant?colossal-australia-65039
05/07/2021, 10:55 PMprovider
set and then later want to set the provider, is there a way to do this without having to recreate the namespace? I've tried updating the statefile directly with the provider I want from the pulumi preview
diff, but Pulumi does like my edits