proud-pizza-80589
03/18/2021, 1:56 PMbumpy-laptop-30846
03/18/2021, 3:18 PMchilly-night-36370
03/20/2021, 2:12 PMkube-prometheus-stack
from <https://prometheus-community.github.io/helm-charts>
. I get the same error for a few of the resources
error: 2 errors occurred:
* the Kubernetes API server reported that "kube-system/kube-prometheus-stack-kube-controller-manager" failed to fully initialize or become live: 'kube-prometheus-stack-kube-controller-manager' timed out waiting to be Ready
* Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods
salmon-ghost-86211
03/22/2021, 10:14 PMaws.iam.Group.get
method to get the group, but I'm not sure how to actually access the existing group membership.
The ultimate goal is to pull in a list of users to apply specific RBAC permissions to. Is there a better way?better-shampoo-48884
03/23/2021, 8:38 AMwet-noon-14291
03/23/2021, 3:56 PMelegant-carpet-8859
03/23/2021, 9:55 PMkind-mechanic-53546
03/24/2021, 12:07 AMbetter-shampoo-48884
03/25/2021, 8:29 AMbetter-shampoo-48884
03/25/2021, 8:29 AMbetter-shampoo-48884
03/25/2021, 8:32 AMbetter-shampoo-48884
03/25/2021, 8:33 AMlemon-monkey-228
03/25/2021, 8:58 AMlemon-monkey-228
03/25/2021, 8:58 AMlemon-monkey-228
03/25/2021, 8:58 AMlemon-monkey-228
03/25/2021, 8:59 AMadorable-action-51248
03/25/2021, 2:37 PMadorable-action-51248
03/26/2021, 9:33 AMbrave-planet-10645
03/26/2021, 11:46 AMkubectl -n <namespace> rollout restart deployment <name>
better-shampoo-48884
03/26/2021, 1:25 PMstocky-student-96739
03/29/2021, 9:29 PMkubernetes:apps/v1:Deployment (web):
error: 2 errors occurred:
* the Kubernetes API server reported that "my-application/web-v845050y" failed to fully initialize or become live: 'web-v845050y' timed out waiting to be Ready
* Attempted to roll forward to new ReplicaSet, but minimum number of Pods did not become live
If I watch the cluster I can see all of the pods (2) in the RS stand up and become Ready, and the ReplicaSet/Deployment reports them all as up + Ready/Up-to-Date inside of 2 minutes. This is happening for every Deployment I have configured on this cluster.
Tried latest @pulumi/kubernetes
Node module, I’m on latest Pulumi CLI binary, on EKS 1.19. I tried blowing everything up and redeploying. Nothing of note when describing the Deployment or ReplicaSet. It’s like the Pulumi client is just ignoring the state of the ReplicaSet.
Any assistance would be appreciated, there’s very little out there on the Googles other than what I’ve already tried.ancient-megabyte-79588
03/29/2021, 11:20 PMancient-megabyte-79588
03/29/2021, 11:20 PMimport
and an import
of the resource group and and the cli always shows as wanting to replace it. The details
(when trying to import
)doesn't seem to indicate why it wants to replace it.
=>azure:core/resourceGroup:ResourceGroup: (import-replacement) 🔒
[urn=urn:pulumi:dpts-shared::KubernetesCluster::azure:core/resourceGroup:ResourceGroup::rg-kubernetes]
[provider=urn:pulumi:dpts-shared::KubernetesCluster::pulumi:providers:azure::default_3_52_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
name: "rg-kubernetes"
+-azure:core/resourceGroup:ResourceGroup: (replace) 🔒
[id=/subscriptions/ad73ec2e-0337-4de5-983c-3944fcb68be8/resourceGroups/rg-kubernetes]
[urn=urn:pulumi:dpts-shared::KubernetesCluster::azure:core/resourceGroup:ResourceGroup::rg-kubernetes]
[provider: urn:pulumi:dpts-shared::KubernetesCluster::pulumi:providers:azure::default_3_6_1::09b02d81-f05d-4347-a5d2-831be11283e0 => urn:pulumi:dpts-shared::KubernetesCluster::pulumi:providers:azure::default_3_52_1::output<string>]
id : "/subscriptions/ad73ec2e-0337-4de5-983c-3944fcb68be8/resourceGroups/rg-kubernetes"
location: "centralus"
name : "rg-kubernetes"
Do you have any insights as to how I can get my pulumi app to not touch this resource-group? I've added the protect
statement to it and I've also added a lock
in the Azure Portal. I do NOT want to accidentally delete all of our control planes and subsequently delete all of the clusters.ancient-megabyte-79588
03/29/2021, 11:32 PMsticky-match-71841
03/30/2021, 11:37 AMhandsome-state-59775
03/30/2021, 2:55 PMerror: resource default/azure-secret was not successfully created by the Kubernetes API server : secrets "azure-secret" already exists
but:
$ KUBECONFIG=./kube.yaml k get secret azure-secret -n default
Error from server (NotFound): secrets "azure-secret" not found
any leads for debugging this? kube.yaml is from: p stack output kubeconfig --show-secrets > kube.yaml
handsome-state-59775
03/30/2021, 4:08 PMbusy-soccer-65968
03/31/2021, 4:47 PMapiVersion
on an ingress is different than what it actually is. Basically in reality my ingress is extensions/v1beta1
but when I refresh pulumi changes state to <http://networking.k8s.io/v1|networking.k8s.io/v1>
and then when I preview it shows it wanting to change it to extensions/v1beta1
which it already is... I'm also seeing this Ingress has at least one rule that does not target any Service. Field '.spec.rules[].http.paths[].backend.serviceName' may not match any active Service
which is also around this helmchart and ingress. I found an issue form 2020 around this. Basically then it was simply a misconfigured helmchart. However, I have confirmed that my labels are correct and my label selectors all line up.limited-rain-96205
03/31/2021, 8:04 PM--replace
requires that you specify each resource, but there are quite a lot, I just want it to clobber everything.limited-rainbow-51650
04/01/2021, 12:01 PMProvider
class but that doesn’t expose the info. Is there a standard way of getting this using the pulumi-kubernetes
provider?