ansible/awx-operator

Inability to overwrite namespace when using awx-operator chart

Open

#999 opened on Jul 27, 2022

View on GitHub
 (3 comments) (3 reactions) (0 assignees)Jinja (712 forks)auto 404
Hacktoberfestgood first issuetype:bug

Repository metrics

Stars
 (1,488 stars)
PR merge metrics
 (PR metrics pending)

Description

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

When deployment is created using helm + terraform after setting namespaces to different than awx, release is still created in awx namespace.

AWX Operator version

0.25.0

AWX version

21.3.0

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.21.12-gke.1500

Modifications

no

Steps to reproduce

resource "helm_release" "awx_operator" {
  name                = "awx-operator"
  namespace       = "awx-operator"
  chart                 = "awx-operator"
  version             = "0.25.0"
  repository         = "https://ansible.github.io/awx-operator"
}

Result should be the same when deployment is done directly by help with given namespace flag

Expected results

All release resources are created ion given namespace

Actual results

Some resources have hardcoded version of namespace: awx and are deployed in other namespace

Additional information

No response

Operator Logs

No response

Contributor guide

Research direction
Examine the Helm chart templates in the repository to find where the default namespace 'awx' is hardcoded, and trace the operator code to see how the namespace is passed to the AWX instance. Look for inconsistencies between the chart's namespace override and the operator's default namespace.
Tech stack
go
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesHelm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60