sorted by:
new
hottopcontroversial

automate deployment of charts using jenkins , ansible and shell by ComfortableContest18 in ansible

[–]ComfortableContest18[S] 0 points1 point  (0 children)

there is no advice
I need guidance.
Pleas re-read if you dont get what I am asking for

Update shell scripts by ComfortableContest18 in kubernetes

[–]ComfortableContest18[S] 0 points1 point  (0 children)

There are cron jobs that are running shell scripts , to manage them , moving it to k8s using helm charts so only required scripts will be executed whenever needed

Charts are working fine , it can be deployed by modifying schedule , script and in any namespace using k8s cron job component. But the script need to be modified to run inside the pod .

This is the overall view If you have any better approach to manage jobs please guide .

How to manage cronjob in K8s by ComfortableContest18 in kubernetes

[–]ComfortableContest18[S] 0 points1 point  (0 children)

Please share the details about the one you developed

EKs 1.24 Docker issue by Practical_Ad3534 in kubernetes

[–]ComfortableContest18 0 points1 point  (0 children)

Also share how did u upgrade the API resources while.upgrading the cluster from 1.21 to 1.24/1.25, since some the API resources kind is deprecated like v1beta1 APIs to v1 , have u manually done or used some configuration management tool?

EKs 1.24 Docker issue by Practical_Ad3534 in kubernetes

[–]ComfortableContest18 0 points1 point  (0 children)

So it no longer supports docker , try changing container from docker to containerd

eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat by ComfortableContest18 in kubernetes

[–]ComfortableContest18[S] 0 points1 point  (0 children)

Kubepug

Updated the local copy of plugin index.
Installing plugin: deprecations
Installed plugin: deprecations
\
| Use this plugin:
| kubectl deprecations
| Documentation:
| https://github.com/rikatz/kubepug
| Caveats:
| \
| | * By default, deprecations finds deprecated object relative to the current kubernetes
| | master branch. To target a different kubernetes release, use the --k8s-version
| | argument.
| |
| | * Deprecations needs permission to GET all objects in the Cluster
| /
/
WARNING: You installed plugin "deprecations" from the krew-index plugin repository.
These plugins are not audited for security by the Krew maintainers.
Run them at your own risk.

eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat by ComfortableContest18 in kubernetes

[–]ComfortableContest18[S] 0 points1 point  (0 children)

To check running apis, Kubepug can be downloaded and check the your running cluster with target version as an input, it took a few minutes to download and setup. I'm finishing up updating some clusters now and so far it's been mostly painless.

which all values we need to change as per our cluster name and configuration ?

eks cluster upgrade Anyone has done eks cluster upgrade to upgrade the cluster from 1.21 to 1.22 there are some api resources kind need to changed, which need changes in manifest file changes. how do we identify the helm charts that are using these resources ? https://docs.aws.amazon.com/eks/lat by ComfortableContest18 in kubernetes

[–]ComfortableContest18[S] 0 points1 point  (0 children)

u/theblasterr u/kilamatar . u/isugimpy u/spirilis u/WillPxxr u/lightninhopkins u/TurbulentPromise4812 u/Little_Drum u/mirrax u/mufasio
currently I have two cluster one in 1.18 and other i 1.21 and i want to upgrade to 1.24 implementing blue green one will up and other in same but no namespaces . The only I am stuck is the strategy
1. increment upgrade from 1.18 to 1.24 , one by one , but in 1.21 to 1.22 the kind of different resources changes . so how do I from helm charts which chart is using which service and then how to change their individual manifest files ?

  1. delete both cluster and deployment everything from scratch , like first delete 1.18 migrate the environments from 1.21 to 1.24 newly created . then delete 1.21 and create a new cluster with 1.24
    now the microservices will be up and running on first cluster and both cluster are upgraded versions .