This repository was archived by the owner on May 1, 2020. It is now read-only.
This repository was archived by the owner on May 1, 2020. It is now read-only.
original pod spec persists on resize #1072
Description
What happened:
When resizing a Hub instance, the existing pods from the instance persist with the original memory settings, whilst the new pods spin up using the upscaled params
What you expected to happen:
All pods to scale with same memory settings
How to reproduce it (as minimally and precisely as possible):
update an existing instance to medium from small (tested via the UI only). Restarting the deployment corrects the issue
Screenshots/additional context:
kubectl describe for existing pod
Name: myhub-blackduck-scan-ngrr5
Namespace: hub-k8s
Priority: 0
PriorityClassName: <none>
Node: *** REMOVED ***
Start Time: Mon, 04 Nov 2019 11:10:07 +0000
Labels: app=blackduck
component=scan
name=myhub
version=2019.10.0
Annotations: <none>
Status: Running
IP: 100.96.3.29
Controlled By: ReplicationController/myhub-blackduck-scan
Containers:
scan:
Container ID: docker://87543eef7b81d018759e788beb5c975b774b0e272d78592da9c8ca098c715a58
Image: docker.io/blackducksoftware/blackduck-scan:2019.10.0
Image ID: docker-pullable://blackducksoftware/blackduck-scan@sha256:4f0f34606ab0b17f745c9baaaa8ce4a9fc08260cf465117125e2547438f34de5
Port: 8443/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 04 Nov 2019 11:10:33 +0000
Ready: True
Restart Count: 0
Limits:
memory: 2560M
Requests:
memory: 2560M
Environment Variables from:
myhub-blackduck-config ConfigMap Optional: false
myhub-blackduck-db-config ConfigMap Optional: false
Environment:
HUB_MAX_MEMORY: 2048m
Mounts:
/opt/blackduck/hub/hub-scan/security from dir-scan (rw)
/tmp/secrets/HUB_POSTGRES_ADMIN_PASSWORD_FILE from db-passwords (rw,path="HUB_POSTGRES_ADMIN_PASSWORD_FILE")
/tmp/secrets/HUB_POSTGRES_USER_PASSWORD_FILE from db-passwords (rw,path="HUB_POSTGRES_USER_PASSWORD_FILE")
/var/run/secrets/kubernetes.io/serviceaccount from default-token-95kkd (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
dir-scan:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit: <unset>
db-passwords:
Type: Secret (a volume populated by a Secret)
SecretName: myhub-blackduck-db-creds
Optional: false
default-token-95kkd:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-95kkd
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events: <none>
Environment (please complete the following information):
- Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.10", GitCommit:"7a578febe155a7366767abce40d8a16795a96371", GitTreeState:"clean", BuildDate:"2019-05-01T04:05:01Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
-
Cloud provider or hardware configuration:
AWS EC2 -
OS (e.g:
cat /etc/os-release):
RHEL 7.6 -
Kernel (e.g.
uname -a):
Linux 3.10.0-957.el7.x86_64