bitter-application-91815
09/23/2020, 1:05 PMbitter-application-91815
09/23/2020, 1:05 PMsalmon-account-74572
09/23/2020, 10:16 PMkustomize
support that transformations "happen in memory, and are not persisted to disk." Is this still true if the RenderYamlToDirectory
property is set on the Kubernetes provider?salmon-account-74572
09/23/2020, 11:00 PMapiVersion: <http://kustomize.config.k8s.io/v1beta1|kustomize.config.k8s.io/v1beta1>
kind: Kustomization
resources:
- ../../base
and I'd like to add this to that YAML:
patchesJson6902:
- path: name.json
target:
group: <http://infrastructure.cluster.x-k8s.io|infrastructure.cluster.x-k8s.io>
kind: AWSCluster
name: base
version: v1alpha3
Is this possible using a transformation?fierce-memory-34976
09/24/2020, 2:46 PMmessage: 'the HPA was unable to compute the replica count: missing request for cpu'
bitter-application-91815
09/24/2020, 8:05 PMbitter-application-91815
09/24/2020, 8:05 PMwitty-vegetable-61961
09/25/2020, 9:48 PMworried-city-86458
09/29/2020, 3:35 AMvpc-resource-controller-role
cluster role, vpc-resource-controller-role-binding
cluster role binding, and vpc-resource-controller
service account already exist after standing up a new eks cluster, while the vpc-resource-controller
deployment does not exist, but the cluster role is different from the guide's download link and is missing config map access (so needs modification anyway),
... so I want to delete the lot iff they exist (and not managed by pulumi) and create new ones with consistent vpc-resource-controller
names throughout, which would leave duplicates for cluster role and cluster role binding and clashes with the service account if I can't delete the pre-existing ones first. 🤔worried-city-86458
09/30/2020, 5:11 AMvpc-admission-webhook
?melodic-printer-39640
09/30/2020, 12:00 PMconst nginxController = new k8s.helm.v3.Chart(`core1-${stack}`, {
version: "3.3.0",
chart: "ingress-nginx",
fetchOpts: {
repo: "<https://kubernetes.github.io/ingress-nginx>"
},
values: {
controller: {
admissionWebhooks: {
enabled: true,
patch: {
enabled: true
}
},
service: {
annotations: {
"<http://external-dns.alpha.kubernetes.io/hostname|external-dns.alpha.kubernetes.io/hostname>": "<http://mydomain.net|mydomain.net>"
},
externalTrafficPolicy: 'Local',
},
config: {
"use-forwarded-headers": 'true'
}
}
}
}, { provider: cluster.provider });
melodic-printer-39640
09/30/2020, 12:00 PMmelodic-printer-39640
09/30/2020, 12:01 PMnutritious-flower-51098
09/30/2020, 12:13 PMmelodic-printer-39640
09/30/2020, 12:59 PM"<http://helm.sh/hook|helm.sh/hook>": pre-install,pre-upgrade
from metadata/annotations in Job template than Pulumi creates the Job. It looks like those hooks are not supported porperly: I got this problem while doing clean installmelodic-printer-39640
09/30/2020, 1:52 PMlimited-rainbow-51650
09/30/2020, 3:33 PMexports
to my Pulumi project from a k8s Service
resource but only a single output is created:
exports.temporalFrontendEndpoint = temporal_frontendService.spec.externalName;
exports.temporalFrontEndName = temporal_frontendService.metadata.name;
results in:
--outputs:--
+ temporalFrontEndName: "temporal-frontend-vw2qfr65"
Any idea why the externalName
is not created as an output?mammoth-afternoon-82670
09/30/2020, 6:54 PMmammoth-afternoon-82670
09/30/2020, 6:54 PMmammoth-afternoon-82670
09/30/2020, 6:56 PM--target
into the digitalocean.KubernetesCluster
, which brought a new kubeconfig content, but for some reason it doesn't seem to be used by the provider at all. Still getting configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
flat-insurance-25294
10/01/2020, 8:58 AMloud-battery-37784
10/01/2020, 1:57 PMloud-battery-37784
10/01/2020, 1:58 PMloud-battery-37784
10/01/2020, 2:01 PMflat-insurance-25294
10/01/2020, 6:21 PMpulumi up
runs and the only thing that has changed is the replica count in index.ts
(written using Pulumi APIs) then it shouldn’t really build the docker image again.
But what bothers me is how unclear it is right now.bitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMbitter-application-91815
10/01/2020, 6:25 PMflat-insurance-25294
10/01/2020, 6:26 PMts
export const image = repo.buildAndPushImage("./app");
Running this twice where ./app
hasn’t changed since last time, should be no-op the second time and re-used the image already pushed since last time.
I’d consider it a bug, not sure if I should post an issue, though.