busy-island-31180
07/21/2022, 11:04 PMApplyT
(in Go) on a type like Deployment
where each individual field is an Output
type, but without using All
and having to specify every field?polite-napkin-90098
07/22/2022, 6:57 PMconst monProvider = new k8s.Provider("monprov", {
kubeconfig: kubeConfig,
});
pulumi.log.warn(`${monProvider.cluster}`);
I get
index.ts(184,32): error TS2339: Property 'cluster' does not exist on type 'Provider'.
what am I doing wrong?late-xylophone-81727
07/25/2022, 11:26 AMlast-applied-configuration
. So Pulumi will see for every up changes which does not exist.
Is it possible to not produce this field at all?
I know about the ignoreChanges
property (https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/) but this produces/writes the field anyway, just skips the diff.
Any ideas? Or did I missed something in the docs?
Thank you.straight-crowd-1391
07/25/2022, 11:28 PM$ pulumi config set --secret pulumi-product-k8s-minikube:db_user_password letmein
const user = new postgresql.Role("product_admin_user", {
createDatabase: true,
login: true,
name: "product_admin_user",
password: config.requireSecret("db_user_password")
});
const productSecretMap = new k8s.core.v1.Secret("product-api-secrets", {
metadata: {
namespace: productNamespace.metadata.name
},
data: {
database_password: config.requireSecret("db_user_password").apply(val => val)
}
});
Problem is, the k8s Secret needs the base64 encoded value that, I think, is being retrieved as the salt encoded value from the config.
What exactly is the standard practice here (aside from using a secret manager) to transfer the database password from the config to both the Database Role and Kubernetes Secret?
I figured I could store 2 password values (one base64, the other in the salt encoded) but it doesn’t feel right.freezing-yacht-63937
07/27/2022, 11:21 AMnamespace: traefikNamespace.metadata.name,
and
transformations: [
(obj: any, opts: pulumi.CustomResourceOptions) => {
if (obj.kind === "Service") {
obj.metadata.namespace == traefikNamespace.metadata.name
}
}
],
But work when i set
kubectl config set-context --current --namespace=NAMESPACE
Should i create an own k8s provider with correct namespace, or I am doing something wrong?future-engineer-43277
07/30/2022, 12:14 PMred-salesclerk-85731
07/28/2022, 2:03 PMkubernetes-ingress-nginx
https://github.com/pulumi/pulumi-kubernetes-ingress-nginx/blob/master/schema.json
1. Do I understand correctly these schemas are handcrafted?
2. Is simply creating a PR with the suggested changes enough?
3. (How) can I rebuild the component locally, I don’t have any go experience or worked with these generated components, so any guide is helpful.red-salesclerk-85731
07/28/2022, 2:35 PMkubernetes-ingress-nginx
if the types are all wrong?worried-city-86458
07/29/2022, 4:06 AMbig-potato-91793
08/03/2022, 5:53 PMpulumi up
fail and after it works the second timebrief-helicopter-28120
08/04/2022, 9:35 AMk8s.yaml.ConfigFile
to deploy CRDs into my EKS cluster (typescript) and I run into issues. Btw I'm new to typescript and as well to pulumi. So please kindly bare with me 🙏
Code:
import * as k8s from "@pulumi/kubernetes";
import * as eks from "@pulumi/eks";
export default {
install_crds(cluster: eks.Cluster){
new k8s.yaml.ConfigFile("argocd_namespace", {
file: "kubernetes_cluster_components/namespaces/argocd-namespace.yaml",
}, {providers: { "kubernetes": cluster.provider }});
}
};
Error:
pulumi:pulumi:Stack k8s-moralis-aws-dev-argo-test running. error: an unhandled error occurred: Program exited with non-zero exit code: -1
I0804 09:23:53.878138 22054 deployment_executor.go:162] deploymentExecutor.Execute(...): exiting provider canceller
Type Name Plan Info
pulumi:pulumi:Stack k8s-moralis-aws-dev-argo-test 1 error; 39 messages
Diagnostics:
pulumi:pulumi:Stack (k8s-moralis-aws-dev-argo-test):
Cloud Provider: aws Stack: aws-dev-argo-test
error: an unhandled error occurred: Program exited with non-zero exit code: -1
The error message is not very descriptive, hence difficult to troubleshoot. Can someone please help me here 🙏ambitious-father-68746
08/05/2022, 1:03 AMambitious-agent-35343
08/05/2022, 3:35 PMcurved-morning-41391
08/10/2022, 6:55 PMcalm-iron-40008
08/10/2022, 9:18 PMpulumi up
fails because the cluster is not available… The deployments, services, pods, etc. do NOT wait for the EKS cluster to be available..
configured Kubernetes cluster is unreachable: unable to load schema information from the API server:…
What do I need to do for pushbutton deployment of my apps? (failover, DR, geo-redundancy, etc.)prehistoric-printer-15534
08/12/2022, 10:39 AMdelightful-bear-69098
08/12/2022, 11:29 AMdelightful-bear-69098
08/14/2022, 5:54 PMbillions-glass-17089
08/15/2022, 7:12 PMenableServerSideApply: true
flag to my provider and then ran pulumi preview
and I got this error:
kubernetes:<http://elasticsearch.k8s.elastic.co/v1:Elasticsearch|elasticsearch.k8s.elastic.co/v1:Elasticsearch> (family):
error: error reading from server: EOF
Seems like it's not working with ECK (which I installed via k8s.yaml.ConfigGroup
calm-iron-40008
08/17/2022, 2:33 AMbright-horse-50102
08/19/2022, 9:38 PMfew-pillow-1133
08/20/2022, 4:01 PMException: Cannot read properties of null (reading 'data')
error: TypeError: Cannot read properties of null (reading 'data')
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/cluster.ts:580:103
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:383:31
at Generator.next (<anonymous>)
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/pulumi/output.js:229:12)
at /root/.pulumi/plugins/resource-eks-v0.41.2/node_modules/@pulumi/output.ts:302:65
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error: an unhandled error occurred: Program exited with non-zero exit code: 1
victorious-dusk-75271
08/21/2022, 9:38 PMvictorious-dusk-75271
08/21/2022, 9:41 PMserviceAccount.create: false
but its not picking up
https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller
i have tried both { serviceAccount: { create: false }} and 'serviceAccount.create': falsebored-spoon-83710
08/23/2022, 6:17 PMmillions-judge-24978
08/23/2022, 6:58 PMk8s.Provider
for an existing EKS cluster? I would like to be able to do something like eks.getClusterOutput({...}).provider
, as I would be able to if I had just created with new eks.Cluster({...}).provider
. Failing that, at least how I can generate the kubeconfig
file text from eks.getClusterOutput().something
.victorious-church-57397
08/24/2022, 2:08 PMunable to run program: Error: unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
on pcl-087019550.pp line 0:
1: resource "github_actions_runner_operatorRunner_poolGithubActionRunner" "kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>" {
unknown resource type 'kubernetes:<http://garo.tietoevry.com/v1alpha1:GithubActionRunner|garo.tietoevry.com/v1alpha1:GithubActionRunner>'
Is there anything i can do locally to get the program to recognise the resource type? I'm installing the CRDs etc using helm, but need to deploy the actual deployment separatelybright-horse-50102
08/25/2022, 1:54 AMWaiting for StatefulSet update to roll out (0/n Pods ready)
2. If you do update the pods yourself while Pulumi is waiting, Pulumi will continue to wait on Waiting for StatefulSet update to roll out (n/n Pods ready)
, and eventually error and time out because .status.currentRevision
was not updated to .status.updatedRevision
:
Diagnostics:
kubernetes:apps/v1:StatefulSet (interactions-app):
error: 3 errors occurred:
* the Kubernetes API server reported that "default/interactions-app-b2ecafa3" failed to fully initialize or become live: 'interactions-app-b2ecafa3' timed out waiting to be Ready
* 32 out of 32 replicas succeeded readiness checks
* StatefulSet controller failed to advance from revision "interactions-app-b2ecafa3-646dcff454" to revision "interactions-app-b2ecafa3-569b7cb476"
Relevant issue? https://github.com/pulumi/pulumi-kubernetes/issues/1066victorious-dusk-75271
08/25/2022, 9:20 AMscheme
in in spec? typescript is complaining about it
apiVersion: elbv2.k8s.aws/v1beta1
kind: IngressClassParams
metadata:
name: awesome-class
spec:
scheme: internal
ipAddressType: dualstack
tags:
- key: org
value: my-org
victorious-church-57397
08/26/2022, 3:14 PMCustomResource
to try and deploy an instance of the resource which is configured on the cluster with the helm chart. I've got pulumi creating it, and it all looks good but no pods are actually being deployed, if i manually run kubectl apply -f
on the yaml file, then it works fine but not when ive converted it to a JS object format, cant help but thinking the CustomResource
might not be what im after?