Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readiness check on Service.get() #1238

Closed
Sodki opened this issue Aug 10, 2020 · 1 comment
Closed

Readiness check on Service.get() #1238

Sodki opened this issue Aug 10, 2020 · 1 comment
Assignees
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue

Comments

@Sodki
Copy link

Sodki commented Aug 10, 2020

Problem description

I'm trying to get information on a (pre-installed) Kubernetes service, but Pulumi complains if there are any problems with the pods. In this particular case I'm expecting those pods to be down, but I need to get information from the service so I can perform a deployment and fix them. I'm using Python:

kubernetes.core.v1.Service.get("service",
    "kube-system/kube-dns",
    opts=pulumi.ResourceOptions(provider=kubernetes_provider))

At this point Pulumi gives the following error:

  kubernetes:core:Service (service):
    error: Preview failed: 2 errors occurred:
        * Resource 'kube-dns' was created but failed to initialize
        * Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods

Affected product version(s)

Pulumi v2.8.2
Pulumi-kubernetes v2.4.2

Suggestions for a fix

When I got support in Slack I was asked to submit a bug report, since a .get() was not expected to run a readiness check.

@leezen leezen added this to the current milestone Aug 25, 2020
@leezen leezen removed this from the current milestone Nov 2, 2020
@lblackstone lblackstone added kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue labels Jul 13, 2023
@lblackstone
Copy link
Member

Closing as a duplicate of #1656

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants