Skip to content

Extension uses standard .kube folder for config - could be a problem #213

@chrizzo84

Description

@chrizzo84

Hello together!
We have noticed that the task always goes fix to the directory /home/user_name/.kube/ to store or read the config.
This can be very problematic if there are several self-hosted agents running on one server, because if there are several agents running at the same time, all running in the same user context (which is normally not a problem), then it can happen that e.g. pipeline 1 has stored the config in the folder, a pipeline 2 is started, which in the meantime overwrites the config of pipeline 1. If there would be a delete step in pipeline 1, pipeline 1 could delete resources, which should be touched only by pipeline 2. In fact, Pipeline 1 runs with data from Pipeline 2 at once.
Of course, the workaround would be to create different users for the different agents. But in my opinion, the standard is simply that a task can be given a working directory, or the task simply stores everything that concerns it in the corresponding run, i.e. the agent folder on which the pipeline is currently running.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions