most-lighter-95902
11/27/2021, 3:18 AM/Users/seungchanlee/Documents/create-knative-cluster/node_modules/@pulumi/pulumi/runtime/invoke.js:127
const resp = yield debuggable_1.debuggablePromise(new Promise((innerResolve, innerReject) => monitor.invoke(req, (err, innerResponse) => {
^
<ref *1> TypeError: Cannot read properties of null (reading 'invoke')
at /Users/seungchanlee/Documents/create-knative-cluster/node_modules/@pulumi/pulumi/runtime/invoke.js:127:114
at new Promise (<anonymous>)
at /Users/seungchanlee/Documents/create-knative-cluster/node_modules/@pulumi/pulumi/runtime/invoke.js:127:63
at Generator.next (<anonymous>)
at fulfilled (/Users/seungchanlee/Documents/create-knative-cluster/node_modules/@pulumi/pulumi/runtime/invoke.js:18:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
promise: Promise { <rejected> [Circular *1] }
}
most-lighter-95902
11/27/2021, 3:18 AMpulumi up
more than once with k8s.yaml.ConfigFile
is attempting to delete and recreate resources.most-lighter-95902
11/27/2021, 3:19 AMkubectl
to apply the yaml file directly:most-lighter-95902
11/27/2021, 3:19 AMkubectl apply -f <https://github.com/knative/operator/releases/download/knative-v1.0.0/operator.yaml>
most-lighter-95902
11/27/2021, 3:19 AMmost-lighter-95902
11/27/2021, 3:20 AMmost-lighter-95902
11/27/2021, 4:38 AMConfigGroup
but same issuemammoth-honey-6147
11/29/2021, 5:28 PMprovider
instance:
kubeconfig := toolsCluster.KubeConfig
clusterProvider, err := kubernetes.NewProvider(ctx, "tools-cluster", &kubernetes.ProviderArgs{
Kubeconfig: kubeconfig,
})
For my resource i append pulumi.Provider(clusterProvider)
to use it but I get:
error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://myapiserver>": x509: certificate signed by unknown authority
However I'm using a Letsencrypt cert (production issuer). So I can, for example, do a curl <https://myaipserver>
without needing to supply --insecure
etc. openssl s_client -connect myapiserver:443
also doesn't reveal any cert issueswhite-train-9300
12/01/2021, 6:51 PMstrong-window-52645
12/01/2021, 9:30 PMunsecret()
, but I"m not even sure what should be wrapped, as the entire Deployment.Spec is marked as secret??strong-window-52645
12/01/2021, 11:11 PMwonderful-twilight-70958
12/01/2021, 11:33 PMcrd2pulumi
to have more control over the package.json for example? I'm trying to automate CRD generation and pushing a public npm package. Right now I don't see any way of editing that pre-defined package.json, other than programmatically editing post generation?cuddly-football-51817
12/03/2021, 1:10 AMelegant-window-55250
12/06/2021, 6:01 PMconfigured Kubernetes cluster is unreachable: failed to parse kubeconfig data in `kubernetes:config:kubeconfig`- couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }
This happened after doing some refactoring (deleting >25 resources) in our cluster. Now, I'm not sure how I'm going to continue forward. I can confirm with the same credentials, I can access the cluster using kubectl
. I can also see the resources that Pulumi is trying to delete. There's also no other changes than naming of resources. Can someone point me in the right/a direction?sparse-spring-91820
12/06/2021, 11:12 PM"nginx-ingress-nginx-admission" already exists
etc.
I added:
values: {
controller: {
ingressClassResource: {
name,
enabled: true,
default: false,
controllerValue: `<http://k8s.io/${currentStack}-ingress-nginx|k8s.io/${currentStack}-ingress-nginx>`
},
...
config as described in docs: https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/ .
Also I added
ingressClassName: name,
to the Ingress rule but still doesn't work.
Does anyone know solution?
Thanks 🙌wonderful-twilight-70958
12/07/2021, 1:44 AMwonderful-twilight-70958
12/07/2021, 2:08 PM<Error>
<Code>ServerBusy</Code>
<Message>Egress is over the account limit. RequestId:7acd46a7-b01e-006c-1c73-ebc9f2000000 Time:2021-12-07T14:08:08.9796530Z</Message>
</Error>
big-potato-91793
12/08/2021, 7:53 PMsteep-portugal-37539
12/08/2021, 11:17 PMimportant-vegetable-39003
12/10/2021, 4:52 PMfull-dress-10026
12/11/2021, 12:39 AMmagnificent-tent-53010
12/13/2021, 2:51 AMimportant-vegetable-39003
12/13/2021, 11:40 AMkube2pulumi
?:
unable to run program: Error: Missing item separator
on pcl-546459028.pp line 80:
75: envFrom = [
76: {
77: configMapRef = {
78: name = "global-configmap"
79: },
80: }
81: {
Expected a comma to mark the beginning of the next item.
Seems to be a bug with kube2pulumi?victorious-exabyte-70545
12/14/2021, 9:27 PMfreezing-architect-84290
12/16/2021, 6:02 PMclever-wall-4616
12/18/2021, 1:31 AMall
and apply
but that doesn't stop Pulumi from running it.
I've considered moving the Helm chart creation out of the custom resource and making the custom resource depend on it. While that would probably work, I would prefer to bundle that into the custom resource if possible.
Is there anything you'd suggest to get around this? Thanks in advance.sparse-butcher-73713
12/22/2021, 7:39 AMsparse-butcher-73713
12/23/2021, 7:30 AMsparse-butcher-73713
12/23/2021, 7:30 AMkubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (nginx):
warning: Helm release "nginx-z31ydwbs" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then retry. Reason: failed pre-install: timed out waiting for the condition
error: failed pre-install: timed out waiting for the condition
sparse-butcher-73713
12/23/2021, 7:30 AM