search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

Duplicate replicasets and configmaps after update #268

Closed azaadshatru closed 10 months ago

azaadshatru commented 2 years ago

I have a client site running Viya 4 instance deployed using viya4-deployment tool. Installation works fine but if we have to apply any settings like ODBC or any updates(version updates), we get duplicate pods, configmaps and replicasets after applying. Everything keeps working until we start/stop services. Start of services fails due to duplicate entries.

Pending pods goes away with restart but ConfigMaps and ReplicaSets which gets duplicated every time we apply update and create issues in further start/stop of services.

We have tried both mechanisms of updating(not simultaneously), end result is same:

  1. Automated deployment tool to upgrade: # viya4-deployment –tags “viya,update”
  2. Using kubectl commands with –prune option a. kubectl -n sasviya4aws apply -f site.yaml --selector="sas.com/admin=cluster-api" b. kubectl -n sasviya4aws wait --for condition=established --timeout=60s -l "sas.com/admin=cluster-api" crd c. kubectl -n sasviya4aws apply -f site.yaml --selector="sas.com/admin=cluster-wide" d. kubectl -n sasviya4aws apply --selector="sas.com/admin=cluster-local" -f site.yaml --prune e. kubectl -n sasviya4aws apply --selector="sas.com/admin=namespace" -f site.yaml --prune

We need help. SAS Track 7613615557

thpang commented 2 years ago

Have you tried using replace instead of apply

dhoucgitter commented 10 months ago

Marking as stale/inactive. If there are additional questions, please open a new Github issue.

dhoucgitter commented 10 months ago

Closing #268 as completed.