Helm chart is generating wrong Deployment files #12133
parthasarathicentific
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am running following helm command to setup apache skywalking with PostgreSQL db as backend .. But The deployment is creating wrong deployment yaml file. How to resolve this ..
helm repo add skywalking https://apache.jfrog.io/artifactory/skywalking-helm
Helm created deployment file:
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "1"
meta.helm.sh/release-name: skywalking
meta.helm.sh/release-namespace: skywalking
creationTimestamp: "2024-04-18T16:44:01Z"
generation: 1
labels:
app: skywalking
app.kubernetes.io/managed-by: Helm
chart: skywalking-4.3.0
component: oap
heritage: Helm
release: skywalking
name: skywalking-oap
namespace: skywalking
resourceVersion: "85122837"
uid: c228f135-71d0-496d-842f-4d8a739d4338
spec:
progressDeadlineSeconds: 600
replicas: 2
revisionHistoryLimit: 10
selector:
matchLabels:
app: skywalking
component: oap
release: skywalking
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
app: skywalking
component: oap
release: skywalking
spec:
affinity:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- podAffinityTerm:
labelSelector:
matchLabels:
app: skywalking
component: oap
release: skywalking
topologyKey: kubernetes.io/hostname
weight: 1
containers:
- env:
- name: JAVA_OPTS
value: -Dmode=no-init -Xmx2g -Xms2g
- name: SW_CLUSTER
value: kubernetes
- name: SW_CLUSTER_K8S_NAMESPACE
value: skywalking
- name: SW_CLUSTER_K8S_LABEL
value: app=skywalking,release=skywalking,component=oap
- name: SKYWALKING_COLLECTOR_UID
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.uid
- name: SW_STORAGE
value: postgresql
- name: SW_STORAGE_ES_CLUSTER_NODES
value: elasticsearch:9200
- name: SW_ES_USER
value: xxx
- name: SW_ES_PASSWORD
value: xxx
image: skywalking.docker.scarf.sh/apache/skywalking-oap-server:9.6.0
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
initialDelaySeconds: 15
periodSeconds: 20
successThreshold: 1
tcpSocket:
port: 12800
timeoutSeconds: 1
name: oap
ports:
- containerPort: 11800
name: grpc
protocol: TCP
- containerPort: 12800
name: rest
protocol: TCP
readinessProbe:
failureThreshold: 3
initialDelaySeconds: 15
periodSeconds: 20
successThreshold: 1
tcpSocket:
port: 12800
timeoutSeconds: 1
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: skywalking-oap
serviceAccountName: skywalking-oap
terminationGracePeriodSeconds: 30
status:
conditions:
lastUpdateTime: "2024-04-18T16:44:02Z"
message: Deployment does not have minimum availability.
reason: MinimumReplicasUnavailable
status: "False"
type: Available
lastUpdateTime: "2024-04-18T16:54:03Z"
message: ReplicaSet "skywalking-oap-5d95999fb6" has timed out progressing.
reason: ProgressDeadlineExceeded
status: "False"
type: Progressing
observedGeneration: 1
replicas: 2
unavailableReplicas: 2
updatedReplicas: 2
Beta Was this translation helpful? Give feedback.
All reactions