Upon jelastic environment installation, a token is defined to interact with kubernetes API. With that token, a user can do anything on the cluster. For that reason, it is dangerous not to change it regularly.
However, this is more complicated to do as to say. Indeed, we need an automated way to instruct our gitlab ci / cd that the token changed.
[ ] change token regularly on k8s
[ ] upon k8s token change, adapt gitlab pipelines configuration with the new token
Upon jelastic environment installation, a token is defined to interact with kubernetes API. With that token, a user can do anything on the cluster. For that reason, it is dangerous not to change it regularly.
However, this is more complicated to do as to say. Indeed, we need an automated way to instruct our gitlab ci / cd that the token changed.