white-forest-65475
02/20/2023, 9:26 PMDiagnostics:
kubernetes:core/v1:Service (argocd-server):
error: Preview failed: resource 'blumeops-de4233d6/argocd-server' does not exist
This is the minimal amount of code I’m using which will generate the error… recall from above that argocd_install_manifest is derived from a yaml manifest file ingested by a k8s.yaml.ConfigGroup
.
argocd_service = k8s.core.v1.Service.get(
"argocd-server",
pulumi.Output.concat(namespace.metadata.name, "/argocd-server"),
opts=pulumi.ResourceOptions.merge(opts, pulumi.ResourceOptions(depends_on=argocd_install_manifest)),
)
Am I missing something here? How can I tell pulumi that it’s OK if the service doesn’t exist yet… it should just wait until the manifest is ready?billowy-army-68599
02/20/2023, 9:30 PMwhite-forest-65475
02/20/2023, 9:33 PMbillowy-army-68599
02/20/2023, 9:33 PMConfigFile
resource for install CRDs, everything else you can pipe through kube2pulumi
white-forest-65475
02/20/2023, 9:35 PMbillowy-army-68599
02/20/2023, 9:36 PMkube2pulumi
on that install manifestwhite-forest-65475
02/20/2023, 9:56 PMkube2pulumi
has a bug related to lists of objects with only one key:
❯ kube2pulumi python -f not-crds.yaml
Error: Error: Missing item separator
on pcl-1017078102.pp line 1301:
1298: ports = [
1299: {
1300: containerPort = 5556
1301: }
1302: {
Expected a comma to mark the beginning of the next item.
The relevant section seems to be:
ports:
- containerPort: 5556
- containerPort: 5557
- containerPort: 5558
If I change this to:
ports:
- containerPort: 5556
name: foo
- containerPort: 5557
name: bar
- containerPort: 5558
name: baz
then processing proceeds to the next section where this construct exists.billowy-army-68599
02/20/2023, 9:56 PMwhite-forest-65475
02/20/2023, 9:56 PMminikube tunnel
and localhostbillowy-army-68599
02/20/2023, 11:27 PM