Skip to content

Labels

Labels

32 labels

  • area/argocd

    area/argocd
    Related to Argo CD features and apps.

  • area/cert-manager

    area/cert-manager
    Related to cert-manager and issuers.

  • area/docs

    area/docs
    Related to documentations

  • area/helm

    area/helm
    Related to Helm applications.

  • area/k0s

    area/k0s
    Related to k0s and k0sctl/cfctl features.

  • area/k8s

    area/k8s
    Related to Kubernetes features.

  • area/multus

    area/multus
    Related to Multus CNI.

  • area/others

    area/others
    Related to others Argo applications

  • area/packer

    area/packer
    Related to Packer recipes.

  • area/scripts

    area/scripts
    Related to deployment scripts.

  • area/slurm

    area/slurm
    Related to SLURM.

  • area/traefik

    area/traefik
    Related to Traefik routing

  • area/xcat

    area/xcat
    Related to xCAT provisioning system.

  • breaking-change

    breaking-change
    Indicates that a pull request introduces a breaking change.

  • current-release

    current-release
    The pull request will be merged for the CURRENT release.

  • dependencies

    dependencies
    Pull requests that update a dependency file

  • kind/bug

    kind/bug
    Indicates an unexpected problem or unintended behavior.

  • kind/chore

    kind/chore
    Grunt tasks. No production code change.

  • kind/discussion

    kind/discussion
    Indicates that an issue, pull request, or discussion needs more information.

  • kind/duplicate

    kind/duplicate
    Indicates that an issue, pull request, or discussion already exists.

  • kind/enhancement

    kind/enhancement
    Indicates new feature requests.

  • kind/invalid

    kind/invalid
    Indicates that an issue, pull request, or discussion is no longer relevant.

  • kind/optimization

    kind/optimization
    Decrease the complexity.

  • kind/security

    kind/security
    Unsafe pratices.

  • next-release

    next-release
    The pull request will be merged AFTER the release.

  • S0

    S0
    Very impact on the end user: this issue must be addressed immediately.

  • S1

    S1
    High impact on the end user ; this issue must be addressed as soon as possible.

  • S2

    S2
    Moderate impatc on the end user ; the issue must be adressed when possible.

  • S3

    S3
    Limited impact on the end user ; this issue can be adressed later.

  • status/acknowledged

    status/acknowledged
    Issue has been taken in account by the core team, but no planning is set.