This message was deleted.
s
sparse-intern-71089
03/28/2023, 6:26 PMThis message was deleted.
c
curved-kitchen-24115
03/28/2023, 6:29 PMAlso, it occurred to me that perhaps providers aren't typically cross compatible this way? It would introduce a layer of dependency for example which may make updating pulumi-kubernetes harder.
What sort of guidance exists in terms of understanding whether this sort of cross-package dependence is acceptable or not.
curved-kitchen-24115
03/28/2023, 6:31 PMFWIW, this is my current strategy:
Copy code
pulumi.all([clusterCore.kubeconfig]).apply(([config]) => {
// this leaves some trash around; gitignore manages this.
// not clear if this is nasty; but without updating k8sProvider
// to understand local.Command
const filename = `kubeconfig.${hash(stack)}.json`;
writeFileSync(filename, JSON.stringify(config));
[
"<http://alertmanagerconfigs.monitoring.coreos.com|alertmanagerconfigs.monitoring.coreos.com>",
"<http://alertmanagers.monitoring.coreos.com|alertmanagers.monitoring.coreos.com>",
"<http://podmonitors.monitoring.coreos.com|podmonitors.monitoring.coreos.com>",
"<http://probes.monitoring.coreos.com|probes.monitoring.coreos.com>",
"<http://prometheuses.monitoring.coreos.com|prometheuses.monitoring.coreos.com>",
"<http://prometheusrules.monitoring.coreos.com|prometheusrules.monitoring.coreos.com>",
"<http://servicemonitors.monitoring.coreos.com|servicemonitors.monitoring.coreos.com>",
"<http://thanosrulers.monitoring.coreos.com|thanosrulers.monitoring.coreos.com>",
].forEach(
(crd) =>
new local.Command(
`${stack}-cleanupcrd-${hash(crd)}`,
{
delete: `kubectl delete crd ${crd}`,
environment: {
KUBECONFIG: filename,
},
}
)
);
});eks.ClusterCore@pulumi/ekss
stocky-restaurant-98004
03/28/2023, 6:50 PMWhen you specify an explicit provider (which you usually do not need to do), it needs to be of the same type that that resource belongs to.
command.local.Commandstocky-restaurant-98004
03/28/2023, 6:52 PMIf you want to deploy a K8s resource after creating a K8s cluster in the same program, you'll need to create an explicit K8s provider with the kubeconfig of the cluster you just provisioned.
stocky-restaurant-98004
03/28/2023, 6:53 PMI believe you'll want to create some of these: https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/v1/customresourcedefinition/
c
curved-kitchen-24115
03/28/2023, 8:02 PM👋🏼 @stocky-restaurant-98004 - thanks for your thoughts.
Good to know that cross provider isn't a thing. The error message definitely led me astray a little there.
👍 1
s
stocky-restaurant-98004
03/29/2023, 4:05 PMFeel free to submit an issue to https://github.com/pulumi/pulumi if you'd like that error message improved.
c
curved-kitchen-24115
04/02/2023, 10:09 PMI mean.. I think it would just say "RTFM, don't imagine what the software could do" 😅
The message as interpreted by my brain made me think there was some ability to "magically" interpret provider abilities.
The docs for command do a solid job of illustrating using the env to set the kubeconfig and in my case I just need to write a temp file to reference.
RE: specifying explicit providers "which you usually do not need to do"
I do it because it's possible, in a dev context, for my system config to be referencing a different cluster than what I have pulumi operating on. So I'm explicit about the k8s cluster to interact with.
2 Views
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