prehistoric-sandwich-7272
02/12/2023, 7:24 PMxyz resource 0.0.40 26 MB 50 minutes ago 36 seconds ago
But when I do pulumi up I get these messages:
warning: resource plugin xyz is expected to have version >=0.0.19, but has 0.0.1; the wrong version may be on your path, or this may be a bug in the plugin
warning: resource plugin xyz is expected to have version >=0.0.40, but has 0.0.1; the wrong version may be on your path, or this may be a bug in the plugin
Why does it expect 0.0.19? And how can I make it point to the version I have locally?creamy-monkey-35142
02/13/2023, 6:05 AMpulumi config set --secret secretMessage "it's a secret to everybody"
then I want dev push secret string to our github repo like v1:6N+U5QAQu244Jqp1:1G
,
is possible to generate secret without install pulumi
?helpful-knife-18557
02/13/2023, 3:34 PMadamant-father-26302
02/13/2023, 6:03 PMbig-angle-30002
02/13/2023, 7:20 PMambitious-continent-10899
02/13/2023, 10:25 PMRendering Kubernetes YAML
should have my answer, however that does't let wright my own YAML, which is what I need. This is what my YAML looks like:ambitious-continent-10899
02/13/2023, 10:27 PMapiVersion: "<http://aadpodidentity.k8s.io/v1|aadpodidentity.k8s.io/v1>"
kind: AzureIdentityBinding
metadata:
name: aad-pod-identity
spec:
azureIdentity: "azure-identity"
selector: "aad-pod-identity"gorgeous-printer-90037
02/13/2023, 11:16 PMfreezing-greece-82130
02/13/2023, 11:33 PM"eventType": "AwsApiCall",
my question is: is there a programmatic way I could have done an action that is stack-agnostic that deleted multiple resources?
tysm!!ambitious-continent-10899
02/14/2023, 3:25 AMconst clientId = managedCluster.identityProfile.apply(profileIds => profileIds?.kubeletIdentity.clientId);
However, the clientId is Undefined
at all time. I am ABLE to see the identityProfile
property being filled out in the Pulumi interface under Resource. How can I ensure I am calling the clientId when it's available?dazzling-yak-63062
02/14/2023, 9:24 AMwooden-midnight-61033
02/14/2023, 1:22 PMbig-potato-91793
02/14/2023, 2:08 PMbig-potato-91793
02/14/2023, 2:08 PMbusy-queen-53310
02/14/2023, 3:37 PMYou must install or update .NET to run this application.
Architecture: x64
Framework: '<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>', version '5.0.0' (x64)
.NET location: C:\Program Files\dotnet\
The following frameworks were found:
3.1.4 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
3.1.6 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
3.1.20 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
3.1.32 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
6.0.5 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
6.0.13 at [C:\Program Files\dotnet\shared\<http://Microsoft.AspNetCore.App|Microsoft.AspNetCore.App>]
Learn about framework resolution:
<https://aka.ms/dotnet/app-launch-failed>
To install missing framework, download:
<https://aka.ms/dotnet-core-applaunch?framework=Microsoft.AspNetCore.App&framework_version=5.0.0&arch=x64&rid=win10-x64>
error: an unhandled error occurred: Program exited with non-zero exit code: 2147516566
late-lizard-19909
02/14/2023, 4:15 PMlate-lizard-19909
02/14/2023, 4:15 PMbillions-glass-17089
02/14/2023, 4:49 PMstrong-helmet-83704
02/14/2023, 5:16 PMagreeable-computer-1409
02/14/2023, 6:27 PMpulumi up/preview
in a CI environment which was using the old auth mechanism.
error: failed to initialize discovery client: The gcp auth plugin has been removed.
Please use the "gke-gcloud-auth-plugin" kubectl/client-go credential plugin instead.
See <https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke> for further details
The fix for this seems to be to add a gcloud container clusters get-credentials CLUSTER_NAME
step before running pulumi up
. Up until now we'd been allowing Pulumi to generate a random suffix on all Kubernetes resources including the cluster name (and CI didn't need to know what the cluster name is), but it seems like now we will need to explicitly reference a cluster name in CI to authenticate. This seems fine once a cluster has already been created, but for newly created clusters it seems like we'd need to bring the cluster up once manually, get the name that Pulumi generates, and then update CI to reference the correct cluster name. Does that sound like the intended workflow, or is there another way to manage authentication for clusters with randomly generated names?gifted-fall-44000
02/14/2023, 8:27 PMlate-lizard-19909
02/14/2023, 9:22 PMbitter-painter-79520
02/15/2023, 11:08 AMbitter-kilobyte-77804
02/15/2023, 1:51 PMbright-flag-46266
02/15/2023, 3:02 PMerror: failed to pull chart: failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized
The weird thing is that it works if I do a docker login
to my repository locally and when I logout it doesn't, so it is probably something with regards to the embedded helm CLI that requires authentication and falls back to the environment if it doesn't exist, but I cannot seem to set this correctly. I've tried to use the following https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/#repositoryopts
to set a docker username and password, but that didn't seem to work.
Relevant config so far looks like this
Chart = oci://<ContainerRegistry>/<Chart>,
RepositoryOpts = new RepositoryOptsArgs()
{
Username = <DockerUsername>,
Password = <DockerPassword>,
},
Version = <HelmVersion>
narrow-ghost-95764
02/15/2023, 6:29 PMdelightful-monkey-90700
02/15/2023, 9:35 PMdeleteBeforeReplace
, if that resource needs to replaced the dependencies must also be deleted (because they depend on the parent resource, and the parent resource can't be deleted while they exist) -- this isn't what happens though and the resource can't be deleted, and thus can't be replacedquick-baker-25274
02/15/2023, 10:12 PMfamous-florist-88180
02/16/2023, 5:25 AMmost-napkin-6669
02/16/2023, 2:29 PMecs_instance_profile
resource due to ResourceNotReady: exceeded wait attempts
Then i run update again and its being created normally
I tried using custom_timeouts=pulumi.CustomTimeouts(create='5m')
but it doesn't seem to effect anything, any suggestions on what i'm missing here?