jx3-gitops-repositories / jx3-terraform-eks Goto Github PK

View Code? Open in Web Editor NEW

9.0 5.0 39.0 52 KB

Jenkins X 3.x Infrastructure Git Template for Terraform and EKS for managing cloud resources

License: Apache License 2.0

Shell 10.12% HCL 89.88%

hacktoberfest

jx3-terraform-eks's Introduction

EKS Terraform Quickstart template

Use this template to easily create a new Git Repository for managing Jenkins X cloud infrastructure needs.

We recommend using Terraform to manage the infrastructure needed to run Jenkins X. There can be a number of cloud resources which need to be created such as:

Kubernetes cluster
Storage buckets for long term storage of logs
IAM Bindings to manage permissions for applications using cloud resources

Jenkins X likes to use GitOps to manage the lifecycle of both infrastructure and cluster resources.
This requires two git Repositories to achieve this:

the first, infrastructure resources will be managed by Terraform and will keep resourecs in sync.
the second, the Kubernetes specific cluster resources will be managed by Jenkins X and keep resources in sync.

Prerequisites

A Git organisation that will be used to create the GitOps repositories used for Jenkins X below. e.g. https://github.com/organizations/plan.
Create a git bot user (different from your own personal user) e.g. https://github.com/join and generate a a personal access token, this will be used by Jenkins X to interact with git repositories. e.g. https://github.com/settings/tokens/new?scopes=repo,read:user,read:org,user:email,write:repo_hook,delete_repo,admin:repo_hook
This bot user needs to have write permission to write to any git repository used by Jenkins X. This can be done by adding the bot user to the git organisation level or individual repositories as a collaborator Add the new bot user to your Git Organisation, for now give it Owner permissions, we will reduce this to member permissions soon.
Install terraform CLI - see here
Install jx CLI - see here
For AWS SSO ensure you have installed AWSCLI version 2 - see here. You must then configure it to use Named Profiles - see here

Git repositories

We use 2 git repositories:

Infrastructure git repository for the Terraform configuration to setup/upgrade/modify your cloud infrastructure (kubernetes cluster, IAM accounts, IAM roles, buckets etc)
Cluster git repository to contain the helmfile.yaml file to define the helm charts to deploy in your cluster

We use separate git repositories since the infrastructure tends to change rarely; whereas the cluster git repository changes alot (every time you add a new quickstart, import a project, release a project etc).

Often different teams look after infrastructure; or you may use tools like Terraform Cloud to process changes to infrastructure & review changes to infrastructure more closely than promotion of applications.

Getting started

Note: remember to create the Git repositories below in your Git Organisation rather than your personal Git account else this will lead to issues with ChatOps and automated registering of webhooks

Create and clone your Infrastructure git repository from this GitHub Template https://github.com/jx3-gitops-repositories/jx3-terraform-eks/generate
Create a Cluster git repository from this template https://github.com/jx3-gitops-repositories/jx3-eks-vault/generate
Override the variable defaults in the Infrastructure repository. (E.g, edit variables.tf, set TF_VAR_ environment variables, or pass the values on the terraform command line.)

cluster_version: Kubernetes version for the EKS cluster.
region: AWS region code for the AWS region to create the cluster in.
jx_git_url: URL of the Cluster repository.
jx_bot_username: The username of the git bot user

commit and push any changes to your Infrastructure git repository:

git commit -a -m "fix: configure cluster repository and project"
git push

Define an environment variable to pass the bot token into Terraform:

export TF_VAR_jx_bot_token=my-bot-token

Now, initialise, plan and apply Terraform:

terraform init

terraform plan

terraform apply

Tail the Jenkins X installation logs

$(terraform output follow_install_logs)

Once finished you can now move into the Jenkins X Developer namespace

jx ns jx

and create or import your applications

jx project

If your application is not yet in a git repository, you are asked for a github.com user and token to push the application to git. This user needs administrative permissions to create repository and hooks. It is likely not the same user as the bot user mentioned above.

Terraform Inputs

You can modify the following terraform inputs in main.tf.

For the full list of terraform inputs see the documentation for jenkins-x/terraform-aws-eks-jx

Name	Description	Type	Default	Required
cluster_name	Name of the Kubernetes cluster to create	`string`	`""`	no
cluster_version	Kubernetes version to use for the EKS cluster.	`string`	n/a	yes
force_destroy	Flag to determine whether storage buckets get forcefully destroyed. If set to false, empty the bucket first in the aws s3 console, else terraform destroy will fail with BucketNotEmpty error	`bool`	`false`	no
install_kuberhealthy	Flag to specify if kuberhealthy operator should be installed	`bool`	`true`	no
is_jx2	Flag to specify if jx2 related resources need to be created	`bool`	`false`	no
jx_bot_token	Bot token used to interact with the Jenkins X cluster git repository	`string`	n/a	yes
jx_bot_username	Bot username used to interact with the Jenkins X cluster git repository	`string`	n/a	yes
jx_git_url	URL for the Jenins X cluster git repository	`string`	n/a	yes
nginx_chart_version	nginx chart version	`string`	`"3.12.0"`	no
profile	Profile stored in aws config or credentials file	`string`	n/a	yes
region	AWS region code for creating resources.	`string`	n/a	yes
vault_user	The AWS IAM Username whose credentials will be used to authenticate the Vault pods against AWS	`string`	`""`	no

Outputs

Name	Description
backup_bucket_url	The bucket where backups from velero will be stored
cert_manager_iam_role	The IAM Role that the Cert Manager pod will assume to authenticate
cluster_autoscaler_iam_role	The IAM Role that the Jenkins X UI pod will assume to authenticate
cluster_name	The name of the created cluster
cluster_oidc_issuer_url	The Cluster OIDC Issuer URL
cm_cainjector_iam_role	The IAM Role that the CM CA Injector pod will assume to authenticate
controllerbuild_iam_role	The IAM Role that the ControllerBuild pod will assume to authenticate
docs	Follow Jenkins X 3.x alpha docs for more information
external_dns_iam_role	The IAM Role that the External DNS pod will assume to authenticate
follow_install_logs	Follow Jenkins X install logs
lts_logs_bucket	The bucket where logs from builds will be stored
lts_reports_bucket	The bucket where test reports will be stored
lts_repository_bucket	The bucket that will serve as artifacts repository
tekton_bot_iam_role	The IAM Role that the build pods will assume to authenticate
vault_dynamodb_table	The Vault DynamoDB table
vault_kms_unseal	The Vault KMS Key for encryption
vault_unseal_bucket	The Vault storage bucket
vault_user_id	The Vault IAM user id
vault_user_secret	The Vault IAM user secret

Cleanup

To remove any cloud resources created here:

Manually remove the generated load balancer, for example, through the AWS EC2 console "Load Balancers" tab. The load balancer is currently not cleaned up automatically and may cause the following destroy step to hang and finally fail.
Run:

terraform destroy

Contributing

When adding new variables please regenerate the markdown table

terraform-docs markdown table .

and replace the Inputs section above

Formatting

When developing please remember to format codebase before raising a pull request

terraform fmt -check -diff -recursive

jx3-terraform-eks's People

Contributors

Stargazers

Watchers

jx3-terraform-eks's Issues

Readme instructions are not OK for AWS EKS deployment using Secret Manager

The documentation does not provide accurate instructions for the case of a deployment using the AWS Secret Manager, instead of Vault.
The documentation should instruct to se the following variables in the main.tf file:
Delete "vault_user" parameter
Set "use_vault" to false
Set "use_asm" to true
Set "create_asm_role" to true

s3 bucket error dissalowed ACL due to new policy bucket owner enforced - start date Apr 2023

AWS has updated its default policies for s3 bucket creation, setting bucket owner enforced by default, which disables ACL actions in the bucket. This generates an error that has to be fixed by manualy allowing ACL on all 3 buckets (log, repository, and reports).
A fix is needed to create the s3 buckets with ACL allowed (bypassing the new AWS default)

Too much permissions with "iam::aws:policy/AmazonS3FullAccess"

Hi!

I detected that terraform use a policy iam::aws:policy/AmazonS3FullAccess that is very "strong" to do several task actions in S3
Normally these kinds of policies are blocked by security because you don't need so powerful permissions.

I detected that it only need permissions in these S3 buckets (in my case) :

            "Effect": "Allow",
            "Resource": [
                "arn:aws:s3:::logs-*/*",
                "arn:aws:s3:::reports-*/*",
                "arn:aws:s3:::repository-*/*",
                "arn:aws:s3:::vault-*/*"
            ]

The role iam::aws:policy/AmazonS3FullAccess appears in these files:

.terraform/modules/eks-jx/modules/cluster/irsa.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_bucketrepo/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_cert_manager/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_cluster_autoscaler/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_cm_cainjector/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_controllerbuild/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_external_dns/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_pipeline_visualizer/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_secrets-parameter-store/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_secrets-secrets-manager/examples/iam-group-complete/main.tf
.terraform/modules/eks-jx.cluster.iam_assumable_role_tekton_bot/examples/iam-group-complete/main.tf

In my case, I change in every terraform init this files with other policy name less permissive.

I think it is a good modification for security upgrade to create a less permissive policy for this point during the process or to have the possibility to specify the name of the policy in main.tf if you have already created one for it or in variables.tf the current default option.

Thank you

The iam role name in the cluster does not match that of terraform created role

annotations:
      eks.amazonaws.com/role-arn: arn:aws:iam::{{ .Values.jxRequirements.cluster.project }}:role/{{ .Values.jxRequirements.cluster.clusterName }}-{{ .Values.jxRequirements.cluster.namespace }}-tekton-bot

while the iam role created by terraform is something like

eks.amazonaws.com/role-arn: arn:aws:iam::{{ .Values.jxRequirements.cluster.project }}:role/{{ .Values.jxRequirements.cluster.clusterName }}-tekton-bot

without -{{ .Values.jxRequirements.cluster.namespace }}

jx-build-controller CrashLoopBackOff - could not read Username for 'https://github.com': No such device or address'

Hello,

I followed all the steps mentioned. The EKS cluster is created and the jx operator is installed successfully. But when i see the pods inside jx namespace, i see the two jx-build-controller pods are in status CrashLoopBackOff. When i looked in to the logs, i see this.

FATAL: failed to get cluster requirements: failed to clone cluster git repo https://github.com/awsomedevops/jx-cluster.git: failed to clone repository https://github.com/awsomedevops/jx-cluster.git to directory: /tmp/jx-git-794802922: failed to run 'git clone https://github.com/awsomedevops/jx-cluster.git /tmp/jx-git-794802922' command in directory '/tmp', output: 'Cloning into '/tmp/jx-git-794802922'... fatal: could not read Username for 'https://github.com': No such device or address

I have updated the cluster git URL and the github bot username correctly in the variables.tf. Could you please help me what is the issue here?

getting-started EKS-JX3

Hi there
I see a lot of changes/improvements (good job)

I am trying to follow the steps:
https://github.com/jx3-gitops-repositories/jx3-terraform-eks#getting-started

but for me nr: 3 is quite hard to understand,
3. You need to configure the git URL of your Cluster git repository into the Infrastructure git repository.
where to configure(which file)?

My understanding is: after I completed
2. Create a Cluster git repository from this template https://github.com/jx3-gitops-repositories/jx3-eks-vault/generate

I will have a git URL and I have to include it in the repo created at stage 1
1. Create and clone your Infrastructure git repository from this GitHub Template https://github.com/jx3-gitops-repositories/jx3-terraform-eks/generate

where exactly(file or) ?

Registry Failed

does anyone face this issue while running pipeline?

loading config with AWS region: 'us-east-1'
--
Let's ensure that we have an ECR repository for the image 
error: failed to lazy create the ECR registry for : failed to check for repository with registry ID : operation error ECR: DescribeRepositories, failed to sign request: failed to retrieve credentials: failed to retrieve credentials, operation error STS: AssumeRoleWithWebIdentity, https response error StatusCode: 400, RequestID: 51e765ba-59c0-4a4d-b3fa-e9b1832f8512, api error InvalidIdentityToken: No OpenIDConnect provider found in your account for

Fresh install fails due to KMS key creation failure.

Cluster cannot be created due to:

module.eks-jx.module.vault.aws_kms_key.kms_vault_unseal[0]: Still creating... [1m40s elapsed]

I suspect that it may be related to hashicorp/terraform-provider-aws#21225 but I have not verified that.

Secrets not auto populating

I installed JX on EKS but secrets don't seem to have auto populated. Any reason why this would have happened?

Error during initial install in terraform

During install on AWS EKS I am receiving the following error:

 Warning: Helm release "jx-git-operator" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then run Terraform again.
│
│   with module.eks-jx.module.cluster.helm_release.jx-git-operator[0],
│   on .terraform\modules\eks-jx\modules\cluster\charts.tf line 1, in resource "helm_release" "jx-git-operator":
│    1: resource "helm_release" "jx-git-operator" {
│
╵
╷
│ Error: timed out waiting for the condition
│
│   with module.eks-jx.module.cluster.helm_release.jx-git-operator[0],
│   on .terraform\modules\eks-jx\modules\cluster\charts.tf line 1, in resource "helm_release" "jx-git-operator":
│    1: resource "helm_release" "jx-git-operator" {
│
╵

Sema Reaction: 🛠️ This code needs a fix

Install jx3 on existing EKS cluster

do we have any chance to install jx3 on existing EKS cluster?

Stuck at boot time

I always get this error at external secret service

{"level":50,"time":1631961555887,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/jenkins-maven-settings"}
{"level":50,"time":1631961555891,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/jenkins-x-chartmuseum"}
{"level":50,"time":1631961555892,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/tekton-git"}
{"level":50,"time":1631961555893,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/jx-basic-auth-user-password"}
{"level":50,"time":1631961555894,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx-staging/tekton-container-registry-auth"}
{"level":50,"time":1631961555896,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/lighthouse-hmac-token"}
{"level":50,"time":1631961555897,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/tekton-container-registry-auth"}
{"level":50,"time":1631961555899,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/lighthouse-oauth-token"}
{"level":50,"time":1631961555911,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/nexus"}
{"level":50,"time":1631961555912,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx/jx-basic-auth-htpasswd"}
{"level":50,"time":1631961555913,"pid":18,"hostname":"kubernetes-external-secrets-7686994b8c-xd2jm","payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret jx-production/tekton-container-registry-auth"}

Few day ago I can start the stack normally, after I changed nexus storage, I always get that even rollback the change. Please advice

Thanks!

JX not installing

After running terraform apply, it shows 87 resources created . However on in octant , the health check shows the following

Check execution error: jx-git-operator/jx-install: error when waiting for pod to start: the khcheck check pod is deleted, waiting for start failed

How do I solve this?

Update to the method for setting defaults for cluster?

The current README has this section:

Override the variable defaults in the Infrastructure repository. (E.g, edit variables.tf, set TF_VAR_ environment variables, or pass the values on the terraform command line.)

region: AWS region code for the AWS region to create the cluster in.
jx_git_url: URL of the Cluster repository.
jx_bot_username: The username of the git bot user

It looks like this should now turn into definitions in jx-requirements,yml, can you confirm? That looks like the pattern, though the only one of the above three variables I see being fetched is "region."

I prefer putting settings into files over setting environment variables, but I'll try the latter if I don't hear back on this relatively soon... thanks.

Fresh install fails on terraform plan

I tried following the getting started guide according to the README with fresh repos and as far as I can tell I have all prerequisites setup but it failed in a few ways a long the way.

I found issue #22 which helped me get passed the initial terraform init error by removing the ref as suggested and running with terraform init -upgrade.

But while @mrmarcsmith managed to run terraform plan I get the following error:

I take it it fails to fetch the needed iam user/role for the eks worker? Is this something that the terraform scripts are creating or am I failing in providing something?

As you probably can tell I'm new to Terraform and have tried looking for information to get around this but failed.

I've tried with different versions of the jx-eks module with the latest being 1.16.1.

As others have managed to bypass the plan step I take it I'm missing something, but I've gone through the readme several times and fail to see what, and being new to Terraform is kind of crippling in this case.

Happy to provide any other information needed.
Hoping anyone is able to see what I'm missing
Thanks

Confusion on versioning

Quick Question: in main.tf what purpose does the ?ref=v1.15.12 serve? aren't we defining the version on the next line down?

  source               = "jenkins-x/eks-jx/aws?ref=v1.15.12"
  version              = "1.15.38"

JX-GitOperator fails to install - failed to download - helm

Hello,

When I run a fresh install of the jxv3 from this repository, my EKS clusters are installed and it fails to install the jx-git-operator with the below error from terraform

module.eks-jx.module.cluster.null_resource.kubeconfig: Creation complete after 2s [id=6616726043172466068]
module.eks-jx.module.cluster.helm_release.jx-git-operator[0]: Creating...

Error: failed to download "https://jenkinsxio.storage.googleapis.com/charts/jx-git-operator-0.0.143.tgz" (hint: running helm repo update may help)

Could you please help me to overcome this? I'm just following the readme from this Git repo.

Install fails on eks 1.21

I tried creating jenkins x cluster by:

templating this repo, setting version to latest (1.17.2), and setting required variables (region, cluster_version = 1.21, jx_git_url, jx_bot_username, jx_bot_token)
templating cluster repo from https://github.com/jx3-gitops-repositories/jx3-eks-vault and making no changes
running terraform apply

Secrets appear to never be created and various pods never start (similar to #16)

If I destroy the deployment, delete all state files, delete and re-template the cluster repo, change the cluster_version to 1.20, and run terraform apply again, jenkins x eventually comes up with everything running. (In contrast to report in #22. Deleting the cluster repo is required, as changes made by jx seem to prevent a new deploy from working.)

jx admin log for 1.21:

jx gitops git setup
setup git user  email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkins-recognia-com email:
jx gitops apply
found last commit message: Initial commit
make regen-phase-1
make[1]: Entering directory '/workspace/source'
jx gitops git setup
setup git user  email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkins-recognia-com email:
Already up to date.
jx gitops requirements merge
wrote the ConfigMap jx-requirements.yml to /tmp/671956249
WARNING: validation failures in YAML file /tmp/671956249: (root): Additional property gitops is not allowed, (root): Additional property kaniko is not allowed, (root): Additional property versionStream is not allowed
saved file /workspace/source/jx-requirements.yml
jx gitops requirements resolve -n
modified the chart repository in /workspace/source/jx-requirements.yml
WARNING: no email in secret jx-boot in namespace jx-git-operator
modified the pipeline user in /workspace/source/jx-requirements.yml
no resolve logic for kubernetes provider eks
jx gitops repository create
file does not exist: .jx/gitops/source-config.yaml so not defaulting any SourceConfig resources
jx gitops repository resolve --source-dir config-root/namespaces
jx gitops jenkins jobs
the source config file .jx/gitops/source-config.yaml does not exist
jx secret convert edit
jx gitops helmfile resolve
jx gitops image -s .jx/git-operator
helmfile --file helmfile.yaml template --validate --include-crds --output-dir-template /tmp/generate/{{.Release.Namespace}}/{{.Release.Name}}
Adding repo jetstack https://charts.jetstack.io
"jetstack" has been added to your repositories

Adding repo bitnami https://charts.bitnami.com/bitnami
"bitnami" has been added to your repositories

Adding repo stable https://charts.helm.sh/stable
"stable" has been added to your repositories

Adding repo jxgh https://jenkins-x-charts.github.io/repo
"jxgh" has been added to your repositories

Templating release=jxboot-helmfile-resources, chart=jxgh/jxboot-helmfile-resources
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-serviceaccount.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-sa.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-sa.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-basic-auth-htpasswd-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-basic-auth-user-password-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/maven-settings-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/tekton-container-registry-auth-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/tekton-git-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/ingress-config-configmap.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-docker-registry.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-extensions-config.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/kapp-config.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-clusterrole.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-aggregate-view.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-clusterrolebinding.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/committer-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-pipeline-activity-reporter-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-view-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/owner-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/viewer-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-rolebinding.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-rb.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-rb.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-cronjob.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-cronjob.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-chartmuseum-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-hook-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-nexus-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/repositories.yaml


Templating release=jenkins-x-crds, chart=jxgh/jenkins-x-crds
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/environments-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/pipelineactivities-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/releases-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/sourcerepositories-crd.yaml


Templating release=jx-pipelines-visualizer, chart=jxgh/jx-pipelines-visualizer
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/service.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/deployment.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/ingress.yaml


Templating release=jx-preview, chart=jxgh/jx-preview
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-sa.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/previews.preview.jenkins.io.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-clusterrole.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-clusterrolebinding.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-role.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-rb.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-cj.yaml


Templating release=lighthouse, chart=jxgh/lighthouse
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/hmacsecret.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/oauthsecret.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/config-external-plugins.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/lighthousebreakpoints-crd.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/lighthousejobs-crd.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-cj.yaml


Templating release=nexus, chart=jxgh/nexus
wrote /tmp/generate/jx/nexus/nexus/templates/secret.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/config.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/pvc.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/service.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/deployment.yaml


Templating release=chartmuseum, chart=stable/chartmuseum
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/secret.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/pvc.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/service.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/deployment.yaml


Templating release=jx-build-controller, chart=jxgh/jx-build-controller
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/serviceaccount.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/clusterrole.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/clusterrolebinding.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/role.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/rolebinding.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/deployment.yaml


Templating release=health-checks-jx, chart=jxgh/jx-kh-check
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-bot-token.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml


Adding repo ingress-nginx https://kubernetes.github.io/ingress-nginx
"ingress-nginx" has been added to your repositories

Templating release=nginx-ingress, chart=ingress-nginx/ingress-nginx
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-poddisruptionbudget.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-serviceaccount.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-configmap.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/clusterrole.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/clusterrolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-role.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-rolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service-metrics.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service-webhook.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-deployment.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/validating-webhook.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/serviceaccount.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/clusterrole.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/clusterrolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/role.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/rolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/job-createSecret.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/job-patchWebhook.yaml


Adding repo external-secrets https://external-secrets.github.io/kubernetes-external-secrets
"external-secrets" has been added to your repositories

Adding repo banzaicloud-stable https://kubernetes-charts.banzaicloud.com
"banzaicloud-stable" has been added to your repositories

Templating release=kubernetes-external-secrets, chart=external-secrets/kubernetes-external-secrets
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/crds/kubernetes-client.io_externalsecrets_crd.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/serviceaccount.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/service.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/deployment.yaml


Templating release=pusher-wave, chart=jxgh/pusher-wave
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/serviceaccount.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/clusterrole.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/clusterrolebinding.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/deployment.yaml


Adding repo cdf https://cdfoundation.github.io/tekton-helm-chart
"cdf" has been added to your repositories

Templating release=tekton-pipeline, chart=cdf/tekton-pipeline
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-ns.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-podsecuritypolicy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-bot-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/webhook-certs-secret.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-artifact-bucket-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-artifact-pvc-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-defaults-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-leader-election-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-logging-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-observability-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-registry-cert-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/feature-flags-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelines-info-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/clustertasks.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/conditions.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelineresources.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelineruns.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelines.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/runs.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/taskruns.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tasks.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-aggregate-edit-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-aggregate-view-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-cluster-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-tenant-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-cluster-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-cluster-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-tenant-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-cluster-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-info-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-leader-election-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-leaderelection-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-info-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-leaderelection-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-svc.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-svc.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-deploy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-deploy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-horizontalpodautoscaler.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/webhook.pipeline.tekton.dev-mutwebhookcfg.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config.webhook.pipeline.tekton.dev-valwebhookcfg.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/validation.webhook.pipeline.tekton.dev-valwebhookcfg.yaml


jx gitops split --dir /tmp/generate
jx gitops rename --dir /tmp/generate
jx gitops helmfile move --output-dir config-root --dir /tmp/generate --dir-includes-release-name
jx secret convert --source-dir config-root -r jx-vault
jx secret replicate --selector secret.jenkins-x.io/replica-source=true
jx gitops namespace --dir-mode --dir config-root/namespaces
jx gitops helmfile report
namespace cert-manager
ignoring release jetstack/cert-manager in namespace cert-manager as using conditional jxRequirementsIngressTLS.enabled

namespace cert-manager
ignoring release jetstack/cert-manager in namespace cert-manager as using conditional jxRequirementsIngressTLS.enabled

namespace jx
ignoring release bitnami/external-dns in namespace jx as using conditional jxRequirementsIngressExternalDNS.enabled
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/nexus-ingress.yaml with api version networking.k8s.io/v1
found jxboot-helmfile-resources version: 1.1.0 https://github.com/jenkins-x-charts/jxboot-helmfile-resources
WARNING: ignoring release jxgh/jenkins-x-crds in namespace jx as we cannot find any generated resources but there is no conditional
ignoring Ingress in file config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml with api version networking.k8s.io/v1
found jx-pipelines-visualizer version: 1.7.5 https://github.com/jenkins-x/jx-pipelines-visualizer
found jx-preview version: 0.0.192 https://github.com/jenkins-x-plugins/jx-preview
found lighthouse version: 1.1.52 https://github.com/jenkins-x/lighthouse
found nexus version: 0.1.41 https://github.com/jenkins-x-charts/nexus
found chartmuseum version: 2.14.2 https://github.com/helm/chartmuseum
found jx-build-controller version: 0.3.9 https://jenkins-x.io/
ignoring release jxgh/acme in namespace jx as using conditional jxRequirementsIngressTLS.enabled
found jx-kh-check version: 0.0.78 https://jenkins-x.io/

namespace jx
ignoring release bitnami/external-dns in namespace jx as using conditional jxRequirementsIngressExternalDNS.enabled
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/nexus-ingress.yaml with api version networking.k8s.io/v1
found jxboot-helmfile-resources version: 1.1.0 https://github.com/jenkins-x-charts/jxboot-helmfile-resources
WARNING: ignoring release jxgh/jenkins-x-crds in namespace jx as we cannot find any generated resources but there is no conditional
ignoring Ingress in file config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml with api version networking.k8s.io/v1
found jx-pipelines-visualizer version: 1.7.5 https://github.com/jenkins-x/jx-pipelines-visualizer
found jx-preview version: 0.0.192 https://github.com/jenkins-x-plugins/jx-preview
found lighthouse version: 1.1.52 https://github.com/jenkins-x/lighthouse
found nexus version: 0.1.41 https://github.com/jenkins-x-charts/nexus
found chartmuseum version: 2.14.2 https://github.com/helm/chartmuseum
found jx-build-controller version: 0.3.9 https://jenkins-x.io/
ignoring release jxgh/acme in namespace jx as using conditional jxRequirementsIngressTLS.enabled
found jx-kh-check version: 0.0.78 https://jenkins-x.io/

namespace kuberhealthy
ignoring release jxgh/kh-tls-check in namespace kuberhealthy as using conditional jxRequirementsTLSCheck.enabled

namespace kuberhealthy
ignoring release jxgh/kh-tls-check in namespace kuberhealthy as using conditional jxRequirementsTLSCheck.enabled

namespace nginx
found ingress-nginx version: 3.12.0 https://github.com/kubernetes/ingress-nginx

namespace nginx
found ingress-nginx version: 3.12.0 https://github.com/kubernetes/ingress-nginx

namespace secret-infra
found kubernetes-external-secrets version: 8.3.0 https://github.com/external-secrets/kubernetes-external-secrets
found pusher-wave version: 0.4.21 https://github.com/pusher/wave

namespace secret-infra
found kubernetes-external-secrets version: 8.3.0 https://github.com/external-secrets/kubernetes-external-secrets
found pusher-wave version: 0.4.21 https://github.com/pusher/wave

namespace tekton-pipelines
found tekton-pipeline version: 0.27.2 https://github.com/cdfoundation/tekton-helm-chart

namespace tekton-pipelines
found tekton-pipeline version: 0.27.2 https://github.com/cdfoundation/tekton-helm-chart

saved docs/releases.yaml
saved docs/README.md
jx gitops scheduler
jx gitops hash --pod-spec --kind Deployment -s config-root/namespaces/jx/lighthouse-config/config-cm.yaml -s config-root/namespaces/jx/lighthouse-config/plugins-cm.yaml -d config-root/namespaces/jx/lighthouse
jx gitops label --dir config-root/cluster                   gitops.jenkins-x.io/pipeline=cluster
jx gitops label --dir config-root/customresourcedefinitions gitops.jenkins-x.io/pipeline=customresourcedefinitions
jx gitops label --dir config-root/namespaces                gitops.jenkins-x.io/pipeline=namespaces
jx gitops annotate --dir config-root --selector app=pusher-wave kapp.k14s.io/change-group=apps.jenkins-x.io/pusher-wave
jx gitops annotate --dir config-root --selector app.kubernetes.io/name=ingress-nginx kapp.k14s.io/change-group=apps.jenkins-x.io/ingress-nginx
jx gitops label --dir config-root/cluster --kind=Namespace team=jx
jx gitops annotate --dir  config-root/namespaces --kind Deployment --selector app=pusher-wave --invert-selector wave.pusher.com/update-on-config-change=true
using kubectl to apply resources
kubectl apply --force --prune -l=gitops.jenkins-x.io/pipeline=customresourcedefinitions -R -f config-root/customresourcedefinitions
customresourcedefinition.apiextensions.k8s.io/environments.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/pipelineactivities.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/releases.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/sourcerepositories.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/previews.preview.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/lighthousebreakpoints.lighthouse.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/lighthousejobs.lighthouse.jenkins.io created
customresourcedefinition.apiextensions.k8s.io/externalsecrets.kubernetes-client.io created
customresourcedefinition.apiextensions.k8s.io/clustertasks.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/conditions.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/pipelineresources.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/pipelineruns.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/pipelines.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/runs.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/taskruns.tekton.dev created
customresourcedefinition.apiextensions.k8s.io/tasks.tekton.dev created
kubectl apply --force --prune -l=gitops.jenkins-x.io/pipeline=cluster                   -R -f config-root/cluster
namespace/jx-production created
namespace/jx-staging created
namespace/jx created
namespace/nginx created
namespace/secret-infra created
clusterrole.rbac.authorization.k8s.io/jx-build-controller-jx created
clusterrolebinding.rbac.authorization.k8s.io/jx-build-controller-jx created
clusterrole.rbac.authorization.k8s.io/jx-pipelines-visualizer created
clusterrolebinding.rbac.authorization.k8s.io/jx-pipelines-visualizer created
clusterrole.rbac.authorization.k8s.io/jx-preview-gc-jobs created
clusterrolebinding.rbac.authorization.k8s.io/jx-preview-gc-jobs created
clusterrole.rbac.authorization.k8s.io/jenkinsx-aggregate-view created
clusterrole.rbac.authorization.k8s.io/tekton-bot created
clusterrolebinding.rbac.authorization.k8s.io/tekton-bot-jx created
clusterrole.rbac.authorization.k8s.io/ingress-nginx created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx created
clusterrole.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-external-secrets-auth created
clusterrole.rbac.authorization.k8s.io/kubernetes-external-secrets created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-external-secrets created
clusterrole.rbac.authorization.k8s.io/pusher-wave-pusher-wave created
clusterrolebinding.rbac.authorization.k8s.io/pusher-wave-pusher-wave created
clusterrole.rbac.authorization.k8s.io/tekton-aggregate-edit created
clusterrole.rbac.authorization.k8s.io/tekton-aggregate-view created
clusterrole.rbac.authorization.k8s.io/tekton-pipelines-controller-cluster-access created
clusterrolebinding.rbac.authorization.k8s.io/tekton-pipelines-controller-cluster-access created
clusterrole.rbac.authorization.k8s.io/tekton-pipelines-controller-tenant-access created
clusterrolebinding.rbac.authorization.k8s.io/tekton-pipelines-controller-tenant-access created
namespace/tekton-pipelines created
clusterrole.rbac.authorization.k8s.io/tekton-pipelines-webhook-cluster-access created
clusterrolebinding.rbac.authorization.k8s.io/tekton-pipelines-webhook-cluster-access created
kubectl apply --force --prune -l=gitops.jenkins-x.io/pipeline=namespaces                -R -f config-root/namespaces
deployment.apps/jenkins-x-chartmuseum created
persistentvolumeclaim/jenkins-x-chartmuseum created
externalsecret.kubernetes-client.io/jenkins-x-chartmuseum created
service/jenkins-x-chartmuseum created
serviceaccount/jenkins-x-controllerbuild created
deployment.apps/jx-build-controller created
rolebinding.rbac.authorization.k8s.io/jx-build-controller created
role.rbac.authorization.k8s.io/jx-build-controller created
kuberhealthycheck.comcast.github.io/jx-bot-token created
rolebinding.rbac.authorization.k8s.io/jx-webhook-check-rb created
rolebinding.rbac.authorization.k8s.io/jx-webhook-events-check-rb created
kuberhealthycheck.comcast.github.io/jx-webhook-events created
serviceaccount/jx-webhook-events-sa created
role.rbac.authorization.k8s.io/jx-webhook-events-service-role created
kuberhealthycheck.comcast.github.io/jx-webhook created
serviceaccount/jx-webhook-sa created
role.rbac.authorization.k8s.io/jx-webhook-service-role created
deployment.apps/jx-pipelines-visualizer created
ingress.networking.k8s.io/jx-pipelines-visualizer created
serviceaccount/jx-pipelines-visualizer created
service/jx-pipelines-visualizer created
cronjob.batch/jx-preview-gc-jobs created
rolebinding.rbac.authorization.k8s.io/jx-preview-gc-jobs created
role.rbac.authorization.k8s.io/jx-preview-gc-jobs created
serviceaccount/jx-preview-gc-jobs created
ingress.networking.k8s.io/chartmuseum created
role.rbac.authorization.k8s.io/committer created
environment.jenkins.io/dev created
sourcerepository.jenkins.io/dev created
rolebinding.rbac.authorization.k8s.io/gcactivities created
role.rbac.authorization.k8s.io/gcactivities created
rolebinding.rbac.authorization.k8s.io/gcpods created
role.rbac.authorization.k8s.io/gcpods created
ingress.networking.k8s.io/hook created
configmap/ingress-config created
externalsecret.kubernetes-client.io/jenkins-maven-settings created
configmap/jenkins-x-docker-registry created
configmap/jenkins-x-extensions created
externalsecret.kubernetes-client.io/jx-basic-auth-htpasswd created
externalsecret.kubernetes-client.io/jx-basic-auth-user-password created
cronjob.batch/jx-gcactivities created
serviceaccount/jx-gcactivities created
cronjob.batch/jx-gcpods created
serviceaccount/jx-gcpods created
role.rbac.authorization.k8s.io/jx-pipeline-activity-updater created
role.rbac.authorization.k8s.io/jx-view created
configmap/kapp-config created
ingress.networking.k8s.io/nexus created
role.rbac.authorization.k8s.io/owner created
environment.jenkins.io/production created
environment.jenkins.io/staging created
rolebinding.rbac.authorization.k8s.io/tekton-bot created
role.rbac.authorization.k8s.io/tekton-bot created
serviceaccount/tekton-bot created
externalsecret.kubernetes-client.io/tekton-container-registry-auth created
externalsecret.kubernetes-client.io/tekton-git created
role.rbac.authorization.k8s.io/viewer created
service/hook created
configmap/lighthouse-external-plugins created
deployment.apps/lighthouse-foghorn created
rolebinding.rbac.authorization.k8s.io/lighthouse-foghorn created
role.rbac.authorization.k8s.io/lighthouse-foghorn created
serviceaccount/lighthouse-foghorn created
cronjob.batch/lighthouse-gc-jobs created
rolebinding.rbac.authorization.k8s.io/lighthouse-gc-jobs created
role.rbac.authorization.k8s.io/lighthouse-gc-jobs created
serviceaccount/lighthouse-gc-jobs created
externalsecret.kubernetes-client.io/lighthouse-hmac-token created
deployment.apps/lighthouse-keeper created
rolebinding.rbac.authorization.k8s.io/lighthouse-keeper created
role.rbac.authorization.k8s.io/lighthouse-keeper created
serviceaccount/lighthouse-keeper created
service/lighthouse-keeper created
externalsecret.kubernetes-client.io/lighthouse-oauth-token created
deployment.apps/lighthouse-tekton-controller created
rolebinding.rbac.authorization.k8s.io/lighthouse-tekton-controller created
role.rbac.authorization.k8s.io/lighthouse-tekton-controller created
serviceaccount/lighthouse-tekton-controller created
service/lighthouse-tekton-controller created
deployment.apps/lighthouse-webhooks created
rolebinding.rbac.authorization.k8s.io/lighthouse-webhooks created
role.rbac.authorization.k8s.io/lighthouse-webhooks created
serviceaccount/lighthouse-webhooks created
configmap/config created
configmap/jx-install-config created
configmap/plugins created
configmap/nexus created
deployment.apps/nexus-nexus created
persistentvolumeclaim/nexus-nexus created
externalsecret.kubernetes-client.io/nexus created
service/nexus created
externalsecret.kubernetes-client.io/tekton-container-registry-auth created
externalsecret.kubernetes-client.io/tekton-container-registry-auth created
service/ingress-nginx-controller-admission created
configmap/ingress-nginx-controller created
deployment.apps/ingress-nginx-controller created
service/ingress-nginx-controller-metrics created
poddisruptionbudget.policy/ingress-nginx-controller created
service/ingress-nginx-controller created
rolebinding.rbac.authorization.k8s.io/ingress-nginx created
role.rbac.authorization.k8s.io/ingress-nginx created
serviceaccount/ingress-nginx created
validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission created
job.batch/ingress-nginx-admission-create created
job.batch/ingress-nginx-admission-patch created
rolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
role.rbac.authorization.k8s.io/ingress-nginx-admission created
serviceaccount/ingress-nginx-admission created
deployment.apps/kubernetes-external-secrets created
serviceaccount/kubernetes-external-secrets created
service/kubernetes-external-secrets created
deployment.apps/pusher-wave-pusher-wave created
serviceaccount/pusher-wave-pusher-wave created
configmap/config-artifact-bucket created
configmap/config-artifact-pvc created
configmap/config-defaults created
configmap/config-leader-election created
configmap/config-logging created
configmap/config-observability created
configmap/config-registry-cert created
validatingwebhookconfiguration.admissionregistration.k8s.io/config.webhook.pipeline.tekton.dev created
configmap/feature-flags created
configmap/pipelines-info created
serviceaccount/tekton-bot created
deployment.apps/tekton-pipelines-controller created
rolebinding.rbac.authorization.k8s.io/tekton-pipelines-controller-leaderelection created
rolebinding.rbac.authorization.k8s.io/tekton-pipelines-controller created
role.rbac.authorization.k8s.io/tekton-pipelines-controller created
serviceaccount/tekton-pipelines-controller created
service/tekton-pipelines-controller created
rolebinding.rbac.authorization.k8s.io/tekton-pipelines-info created
role.rbac.authorization.k8s.io/tekton-pipelines-info created
role.rbac.authorization.k8s.io/tekton-pipelines-leader-election created
podsecuritypolicy.policy/tekton-pipelines created
deployment.apps/tekton-pipelines-webhook created
horizontalpodautoscaler.autoscaling/tekton-pipelines-webhook created
rolebinding.rbac.authorization.k8s.io/tekton-pipelines-webhook-leaderelection created
rolebinding.rbac.authorization.k8s.io/tekton-pipelines-webhook created
role.rbac.authorization.k8s.io/tekton-pipelines-webhook created
serviceaccount/tekton-pipelines-webhook created
service/tekton-pipelines-webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/validation.webhook.pipeline.tekton.dev created
secret/webhook-certs created
mutatingwebhookconfiguration.admissionregistration.k8s.io/webhook.pipeline.tekton.dev created
jx gitops postprocess
there is no post processing Secret jx-post-process in namespace default so not performing any additional post processing steps
jx verify ingress --ingress-service ingress-nginx-controller
Waiting to find the external host name of the ingress controller Service in namespace nginx with name ingress-nginx-controller
The Ingress address ac590dd0ede7c4936a47425532479724-f436271ef857f6f8.elb.us-east-1.amazonaws.com is not an IP address. We recommend we try resolve it to a public IP address and use that for the domain to access services externally.
Waiting for ac590dd0ede7c4936a47425532479724-f436271ef857f6f8.elb.us-east-1.amazonaws.com to be resolvable to an IP address...
WARNING: retrying after error: address cannot be resolved yet ac590dd0ede7c4936a47425532479724-f436271ef857f6f8.elb.us-east-1.amazonaws.com
.
.
.
.
.
.
.
.
.
.
.
.
.

ac590dd0ede7c4936a47425532479724-f436271ef857f6f8.elb.us-east-1.amazonaws.com resolved to IP 35.170.250.137
No domain flag provided so using default 35.170.250.137.nip.io to generate Ingress rules
defaulting the domain to 35.170.250.137.nip.io and modified /workspace/source/jx-requirements.yml
now verifying docker registry ingress setup
jx gitops git setup
found git user.name jenkins-recognia-com from requirements
found git user.email  from requirements
setup git user  email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkins-recognia-com email:
git add --all
git commit -m "chore: regenerated" -m "/pipeline cancel"
[main e214e20] chore: regenerated
 203 files changed, 12529 insertions(+), 108 deletions(-)
 rewrite .jx/secret/mapping/secret-mappings.yaml (61%)
 create mode 100644 config-root/cluster/namespaces/jx-production.yaml
 create mode 100644 config-root/cluster/namespaces/jx-staging.yaml
 create mode 100644 config-root/cluster/namespaces/jx.yaml
 create mode 100644 config-root/cluster/namespaces/nginx.yaml
 create mode 100644 config-root/cluster/namespaces/secret-infra.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-build-controller/jx-build-controller-jx-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-build-controller/jx-build-controller-jx-crb.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-crb.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-preview/jx-preview-gc-jobs-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/jx/jx-preview/jx-preview-gc-jobs-crb.yaml
 create mode 100644 config-root/cluster/resources/jx/jxboot-helmfile-resources/jenkinsx-aggregate-view-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/jx/jxboot-helmfile-resources/tekton-bot-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/jx/jxboot-helmfile-resources/tekton-bot-jx-crb.yaml
 create mode 100644 config-root/cluster/resources/nginx/ingress-nginx-nginx-ingress/ingress-nginx-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/nginx/ingress-nginx-nginx-ingress/ingress-nginx-crb.yaml
 create mode 100644 config-root/cluster/resources/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-crb.yaml
 create mode 100644 config-root/cluster/resources/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-auth-crb.yaml
 create mode 100644 config-root/cluster/resources/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-crb.yaml
 create mode 100644 config-root/cluster/resources/secret-infra/pusher-wave/pusher-wave-pusher-wave-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/secret-infra/pusher-wave/pusher-wave-pusher-wave-crb.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-aggregate-edit-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-aggregate-view-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-cluster-access-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-cluster-access-crb.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-tenant-access-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-tenant-access-crb.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-ns.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-cluster-access-clusterrole.yaml
 create mode 100644 config-root/cluster/resources/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-cluster-access-crb.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/jenkins-x-crds/environments.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/jenkins-x-crds/pipelineactivities.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/jenkins-x-crds/releases.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/jenkins-x-crds/sourcerepositories.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/jx-preview/previews.preview.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/lighthouse/lighthousebreakpoints.lighthouse.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/jx/lighthouse/lighthousejobs.lighthouse.jenkins.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/secret-infra/kubernetes-external-secrets/externalsecrets.kubernetes-client.io-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/clustertasks.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/conditions.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/pipelineresources.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/pipelineruns.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/pipelines.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/runs.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/taskruns.tekton.dev-crd.yaml
 create mode 100644 config-root/customresourcedefinitions/tekton-pipelines/tekton-pipeline/tasks.tekton.dev-crd.yaml
 create mode 100644 config-root/namespaces/jx-production/jxboot-helmfile-resources/tekton-container-registry-auth-secret.yaml
 create mode 100644 config-root/namespaces/jx-staging/jxboot-helmfile-resources/tekton-container-registry-auth-secret.yaml
 create mode 100644 config-root/namespaces/jx/chartmuseum/jenkins-x-chartmuseum-deploy.yaml
 create mode 100644 config-root/namespaces/jx/chartmuseum/jenkins-x-chartmuseum-persistentvolumeclaim.yaml
 create mode 100644 config-root/namespaces/jx/chartmuseum/jenkins-x-chartmuseum-secret.yaml
 create mode 100644 config-root/namespaces/jx/chartmuseum/jenkins-x-chartmuseum-svc.yaml
 create mode 100644 config-root/namespaces/jx/jx-build-controller/jenkins-x-controllerbuild-sa.yaml
 create mode 100644 config-root/namespaces/jx/jx-build-controller/jx-build-controller-deploy.yaml
 create mode 100644 config-root/namespaces/jx/jx-build-controller/jx-build-controller-rb.yaml
 create mode 100644 config-root/namespaces/jx/jx-build-controller/jx-build-controller-role.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-bot-token-kuberhealthycheck.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-check-rb-rb.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-check-rb-rb.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-kuberhealthycheck.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-sa-sa.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-service-role-role.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-kuberhealthycheck.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-sa-sa.yaml
 create mode 100644 config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-service-role-role.yaml
 create mode 100644 config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-deploy.yaml
 create mode 100644 config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml
 create mode 100644 config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-sa.yaml
 create mode 100644 config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-svc.yaml
 create mode 100644 config-root/namespaces/jx/jx-preview/jx-preview-gc-jobs-cronjob.yaml
 create mode 100644 config-root/namespaces/jx/jx-preview/jx-preview-gc-jobs-rb.yaml
 create mode 100644 config-root/namespaces/jx/jx-preview/jx-preview-gc-jobs-role.yaml
 create mode 100644 config-root/namespaces/jx/jx-preview/jx-preview-gc-jobs-sa.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/committer-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/dev-environment.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/dev-sourcerepository.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/gcactivities-rb.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/gcactivities-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/gcpods-rb.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/gcpods-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/ingress-config-cm.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jenkins-maven-settings-secret.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jenkins-x-docker-registry-cm.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jenkins-x-extensions-cm.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-basic-auth-htpasswd-secret.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-basic-auth-user-password-secret.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-gcactivities-cronjob.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-gcactivities-sa.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-gcpods-cronjob.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-gcpods-sa.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-pipeline-activity-updater-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/jx-view-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/kapp-config-cm.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/nexus-ingress.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/owner-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/production-environment.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/staging-environment.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/tekton-bot-rb.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/tekton-bot-role.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/tekton-bot-sa.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/tekton-container-registry-auth-secret.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/tekton-git-secret.yaml
 create mode 100644 config-root/namespaces/jx/jxboot-helmfile-resources/viewer-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse-config/config-cm.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse-config/install-config-cm.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse-config/plugins-cm.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/hook-svc.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-external-plugins-cm.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-foghorn-deploy.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-foghorn-rb.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-foghorn-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-foghorn-sa.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-gc-jobs-cronjob.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-gc-jobs-rb.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-gc-jobs-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-gc-jobs-sa.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-hmac-token-secret.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-keeper-deploy.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-keeper-rb.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-keeper-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-keeper-sa.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-keeper-svc.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-oauth-token-secret.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-tekton-controller-deploy.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-tekton-controller-rb.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-tekton-controller-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-tekton-controller-sa.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-tekton-controller-svc.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-webhooks-deploy.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-webhooks-rb.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-webhooks-role.yaml
 create mode 100644 config-root/namespaces/jx/lighthouse/lighthouse-webhooks-sa.yaml
 create mode 100644 config-root/namespaces/jx/nexus/nexus-cm.yaml
 create mode 100644 config-root/namespaces/jx/nexus/nexus-nexus-deploy.yaml
 create mode 100644 config-root/namespaces/jx/nexus/nexus-nexus-persistentvolumeclaim.yaml
 create mode 100644 config-root/namespaces/jx/nexus/nexus-secret.yaml
 create mode 100644 config-root/namespaces/jx/nexus/nexus-svc.yaml
 create mode 100644 config-root/namespaces/jx/source-repositories/README.md
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-admission-svc.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-cm.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-deploy.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-metrics-svc.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-poddisruptionbudget.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-controller-svc.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-rb.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-role.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/ingress-nginx-sa.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/ingress-nginx-admission-valwebhookcfg.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-create-job.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-patch-job.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-rb.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-role.yaml
 create mode 100644 config-root/namespaces/nginx/ingress-nginx-nginx-ingress/templates/admission-webhooks/job-patch/ingress-nginx-admission-sa.yaml
 create mode 100644 config-root/namespaces/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-deploy.yaml
 create mode 100644 config-root/namespaces/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-sa.yaml
 create mode 100644 config-root/namespaces/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets-svc.yaml
 create mode 100644 config-root/namespaces/secret-infra/pusher-wave/pusher-wave-pusher-wave-deploy.yaml
 create mode 100644 config-root/namespaces/secret-infra/pusher-wave/pusher-wave-pusher-wave-sa.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-artifact-bucket-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-artifact-pvc-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-defaults-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-leader-election-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-logging-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-observability-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config-registry-cert-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/config.webhook.pipeline.tekton.dev-valwebhookcfg.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/feature-flags-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/pipelines-info-cm.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-bot-sa.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-deploy.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-leaderelection-rb.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-rb.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-role.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-sa.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-controller-svc.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-info-rb.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-info-role.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-leader-election-role.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-podsecuritypolicy.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-deploy.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-horizontalpodautoscaler.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-leaderelection-rb.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-rb.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-role.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-sa.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/tekton-pipelines-webhook-svc.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/validation.webhook.pipeline.tekton.dev-valwebhookcfg.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/webhook-certs-secret.yaml
 create mode 100644 config-root/namespaces/tekton-pipelines/tekton-pipeline/webhook.pipeline.tekton.dev-mutwebhookcfg.yaml
make[1]: Leaving directory '/workspace/source'
found last commit message: chore: regenerated

/pipeline cancel
make regen-phase-2
make[1]: Entering directory '/workspace/source'
jx verify ingress --ingress-service ingress-nginx-controller
now verifying docker registry ingress setup
jx gitops repository create
file does not exist: .jx/gitops/source-config.yaml so not defaulting any SourceConfig resources
jx gitops repository resolve --source-dir config-root/namespaces
jx gitops jenkins jobs
the source config file .jx/gitops/source-config.yaml does not exist
jx secret convert edit
jx gitops helmfile resolve
jx gitops image -s .jx/git-operator
helmfile --file helmfile.yaml template --validate --include-crds --output-dir-template /tmp/generate/{{.Release.Namespace}}/{{.Release.Name}}
Adding repo jetstack https://charts.jetstack.io
"jetstack" has been added to your repositories

Adding repo bitnami https://charts.bitnami.com/bitnami
"bitnami" has been added to your repositories

Adding repo stable https://charts.helm.sh/stable
"stable" has been added to your repositories

Adding repo jxgh https://jenkins-x-charts.github.io/repo
"jxgh" has been added to your repositories

Templating release=jxboot-helmfile-resources, chart=jxgh/jxboot-helmfile-resources
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-serviceaccount.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-sa.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-sa.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-basic-auth-htpasswd-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-basic-auth-user-password-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/maven-settings-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/tekton-container-registry-auth-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/tekton-git-secret.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/ingress-config-configmap.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-docker-registry.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-extensions-config.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/kapp-config.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-clusterrole.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jenkins-x-aggregate-view.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-clusterrolebinding.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/committer-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-pipeline-activity-reporter-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-view-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/owner-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/viewer-role.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/build-bot-rolebinding.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-rb.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-rb.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcactivities-cronjob.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/jx-gcpods-cronjob.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-chartmuseum-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-hook-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/700-nexus-ing.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/environments.yaml
wrote /tmp/generate/jx/jxboot-helmfile-resources/jxboot-helmfile-resources/templates/repositories.yaml


Templating release=jenkins-x-crds, chart=jxgh/jenkins-x-crds
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/environments-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/pipelineactivities-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/releases-crd.yaml
wrote /tmp/generate/jx/jenkins-x-crds/jenkins-x-crds/templates/sourcerepositories-crd.yaml


Templating release=jx-pipelines-visualizer, chart=jxgh/jx-pipelines-visualizer
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/rbac.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/service.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/deployment.yaml
wrote /tmp/generate/jx/jx-pipelines-visualizer/jx-pipelines-visualizer/templates/ingress.yaml


Templating release=jx-preview, chart=jxgh/jx-preview
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-sa.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/previews.preview.jenkins.io.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-clusterrole.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-clusterrolebinding.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-role.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-rb.yaml
wrote /tmp/generate/jx/jx-preview/jx-preview/templates/gc-jobs-cj.yaml


Templating release=lighthouse, chart=jxgh/lighthouse
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-sa.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/hmacsecret.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/oauthsecret.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/config-external-plugins.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/lighthousebreakpoints-crd.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/lighthousejobs-crd.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-role.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-rb.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-service.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/foghorn-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/keeper-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/tekton-controller-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/webhooks-deployment.yaml
wrote /tmp/generate/jx/lighthouse/lighthouse/templates/gc-jobs-cj.yaml


Templating release=nexus, chart=jxgh/nexus
wrote /tmp/generate/jx/nexus/nexus/templates/secret.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/config.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/pvc.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/service.yaml
wrote /tmp/generate/jx/nexus/nexus/templates/deployment.yaml


Templating release=chartmuseum, chart=stable/chartmuseum
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/secret.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/pvc.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/service.yaml
wrote /tmp/generate/jx/chartmuseum/chartmuseum/templates/deployment.yaml


Templating release=jx-build-controller, chart=jxgh/jx-build-controller
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/serviceaccount.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/clusterrole.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/clusterrolebinding.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/role.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/rolebinding.yaml
wrote /tmp/generate/jx/jx-build-controller/jx-build-controller/templates/deployment.yaml


Templating release=health-checks-jx, chart=jxgh/jx-kh-check
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-bot-token.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-check.yaml
wrote /tmp/generate/jx/health-checks-jx/jx-kh-check/templates/jx-webhook-events-check.yaml


Adding repo ingress-nginx https://kubernetes.github.io/ingress-nginx
"ingress-nginx" has been added to your repositories

Templating release=nginx-ingress, chart=ingress-nginx/ingress-nginx
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-poddisruptionbudget.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-serviceaccount.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-configmap.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/clusterrole.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/clusterrolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-role.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-rolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service-metrics.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service-webhook.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-service.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/controller-deployment.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/validating-webhook.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/serviceaccount.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/clusterrole.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/clusterrolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/role.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/rolebinding.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/job-createSecret.yaml
wrote /tmp/generate/nginx/nginx-ingress/ingress-nginx/templates/admission-webhooks/job-patch/job-patchWebhook.yaml


Adding repo external-secrets https://external-secrets.github.io/kubernetes-external-secrets
"external-secrets" has been added to your repositories

Adding repo banzaicloud-stable https://kubernetes-charts.banzaicloud.com
"banzaicloud-stable" has been added to your repositories

Templating release=kubernetes-external-secrets, chart=external-secrets/kubernetes-external-secrets
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/crds/kubernetes-client.io_externalsecrets_crd.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/serviceaccount.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/rbac.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/service.yaml
wrote /tmp/generate/secret-infra/kubernetes-external-secrets/kubernetes-external-secrets/templates/deployment.yaml


Templating release=pusher-wave, chart=jxgh/pusher-wave
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/serviceaccount.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/clusterrole.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/clusterrolebinding.yaml
wrote /tmp/generate/secret-infra/pusher-wave/pusher-wave/templates/deployment.yaml


Adding repo cdf https://cdfoundation.github.io/tekton-helm-chart
"cdf" has been added to your repositories

Templating release=tekton-pipeline, chart=cdf/tekton-pipeline
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-ns.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-podsecuritypolicy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-bot-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-sa.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/webhook-certs-secret.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-artifact-bucket-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-artifact-pvc-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-defaults-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-leader-election-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-logging-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-observability-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config-registry-cert-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/feature-flags-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelines-info-cm.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/clustertasks.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/conditions.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelineresources.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelineruns.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/pipelines.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/runs.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/taskruns.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tasks.tekton.dev-crd.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-aggregate-edit-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-aggregate-view-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-cluster-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-tenant-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-cluster-access-clusterrole.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-cluster-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-tenant-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-cluster-access-crb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-info-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-leader-election-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-role.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-leaderelection-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-info-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-leaderelection-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-rb.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-svc.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-svc.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-controller-deploy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-deploy.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/tekton-pipelines-webhook-horizontalpodautoscaler.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/webhook.pipeline.tekton.dev-mutwebhookcfg.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/config.webhook.pipeline.tekton.dev-valwebhookcfg.yaml
wrote /tmp/generate/tekton-pipelines/tekton-pipeline/tekton-pipeline/templates/validation.webhook.pipeline.tekton.dev-valwebhookcfg.yaml


jx gitops split --dir /tmp/generate
jx gitops rename --dir /tmp/generate
jx gitops helmfile move --output-dir config-root --dir /tmp/generate --dir-includes-release-name
jx secret convert --source-dir config-root -r jx-vault
jx secret replicate --selector secret.jenkins-x.io/replica-source=true
jx gitops namespace --dir-mode --dir config-root/namespaces
jx gitops helmfile report
namespace cert-manager
ignoring release jetstack/cert-manager in namespace cert-manager as using conditional jxRequirementsIngressTLS.enabled

namespace cert-manager
ignoring release jetstack/cert-manager in namespace cert-manager as using conditional jxRequirementsIngressTLS.enabled

namespace jx
ignoring release bitnami/external-dns in namespace jx as using conditional jxRequirementsIngressExternalDNS.enabled
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/nexus-ingress.yaml with api version networking.k8s.io/v1
found jxboot-helmfile-resources version: 1.1.0 https://github.com/jenkins-x-charts/jxboot-helmfile-resources
WARNING: ignoring release jxgh/jenkins-x-crds in namespace jx as we cannot find any generated resources but there is no conditional
ignoring Ingress in file config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml with api version networking.k8s.io/v1
found jx-pipelines-visualizer version: 1.7.5 https://github.com/jenkins-x/jx-pipelines-visualizer
found jx-preview version: 0.0.192 https://github.com/jenkins-x-plugins/jx-preview
found lighthouse version: 1.1.52 https://github.com/jenkins-x/lighthouse
found nexus version: 0.1.41 https://github.com/jenkins-x-charts/nexus
found chartmuseum version: 2.14.2 https://github.com/helm/chartmuseum
found jx-build-controller version: 0.3.9 https://jenkins-x.io/
ignoring release jxgh/acme in namespace jx as using conditional jxRequirementsIngressTLS.enabled
found jx-kh-check version: 0.0.78 https://jenkins-x.io/

namespace jx
ignoring release bitnami/external-dns in namespace jx as using conditional jxRequirementsIngressExternalDNS.enabled
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml with api version networking.k8s.io/v1
ignoring Ingress in file config-root/namespaces/jx/jxboot-helmfile-resources/nexus-ingress.yaml with api version networking.k8s.io/v1
found jxboot-helmfile-resources version: 1.1.0 https://github.com/jenkins-x-charts/jxboot-helmfile-resources
WARNING: ignoring release jxgh/jenkins-x-crds in namespace jx as we cannot find any generated resources but there is no conditional
ignoring Ingress in file config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml with api version networking.k8s.io/v1
found jx-pipelines-visualizer version: 1.7.5 https://github.com/jenkins-x/jx-pipelines-visualizer
found jx-preview version: 0.0.192 https://github.com/jenkins-x-plugins/jx-preview
found lighthouse version: 1.1.52 https://github.com/jenkins-x/lighthouse
found nexus version: 0.1.41 https://github.com/jenkins-x-charts/nexus
found chartmuseum version: 2.14.2 https://github.com/helm/chartmuseum
found jx-build-controller version: 0.3.9 https://jenkins-x.io/
ignoring release jxgh/acme in namespace jx as using conditional jxRequirementsIngressTLS.enabled
found jx-kh-check version: 0.0.78 https://jenkins-x.io/

namespace kuberhealthy
ignoring release jxgh/kh-tls-check in namespace kuberhealthy as using conditional jxRequirementsTLSCheck.enabled

namespace kuberhealthy
ignoring release jxgh/kh-tls-check in namespace kuberhealthy as using conditional jxRequirementsTLSCheck.enabled

namespace nginx
found ingress-nginx version: 3.12.0 https://github.com/kubernetes/ingress-nginx

namespace nginx
found ingress-nginx version: 3.12.0 https://github.com/kubernetes/ingress-nginx

namespace secret-infra
found kubernetes-external-secrets version: 8.3.0 https://github.com/external-secrets/kubernetes-external-secrets
found pusher-wave version: 0.4.21 https://github.com/pusher/wave

namespace secret-infra
found kubernetes-external-secrets version: 8.3.0 https://github.com/external-secrets/kubernetes-external-secrets
found pusher-wave version: 0.4.21 https://github.com/pusher/wave

namespace tekton-pipelines
found tekton-pipeline version: 0.27.2 https://github.com/cdfoundation/tekton-helm-chart

namespace tekton-pipelines
found tekton-pipeline version: 0.27.2 https://github.com/cdfoundation/tekton-helm-chart

saved docs/releases.yaml
saved docs/README.md
jx gitops scheduler
jx gitops hash --pod-spec --kind Deployment -s config-root/namespaces/jx/lighthouse-config/config-cm.yaml -s config-root/namespaces/jx/lighthouse-config/plugins-cm.yaml -d config-root/namespaces/jx/lighthouse
jx gitops label --dir config-root/cluster                   gitops.jenkins-x.io/pipeline=cluster
jx gitops label --dir config-root/customresourcedefinitions gitops.jenkins-x.io/pipeline=customresourcedefinitions
jx gitops label --dir config-root/namespaces                gitops.jenkins-x.io/pipeline=namespaces
jx gitops annotate --dir config-root --selector app=pusher-wave kapp.k14s.io/change-group=apps.jenkins-x.io/pusher-wave
jx gitops annotate --dir config-root --selector app.kubernetes.io/name=ingress-nginx kapp.k14s.io/change-group=apps.jenkins-x.io/ingress-nginx
jx gitops label --dir config-root/cluster --kind=Namespace team=jx
jx gitops annotate --dir  config-root/namespaces --kind Deployment --selector app=pusher-wave --invert-selector wave.pusher.com/update-on-config-change=true
jx gitops git setup
found git user.name jenkins-recognia-com from requirements
found git user.email  from requirements
setup git user  email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkins-recognia-com email:
git add --all
git commit -m "chore: regenerated" -m "/pipeline cancel"
[main 9cfac1a] chore: regenerated
 17 files changed, 18 insertions(+), 18 deletions(-)
make[1]: Leaving directory '/workspace/source'
make regen-phase-3
make[1]: Entering directory '/workspace/source'
Already up to date.
To https://github.com/Recognia/cluster-operations-testing
   56cc328..9cfac1a  main -> main
VAULT_ADDR=https://vault.jx-vault:8200 VAULT_NAMESPACE=jx-vault jx secret populate --secret-namespace jx-vault
waiting for vault pod vault-0 in namespace jx-vault to be ready...
pod vault-0 in namespace jx-vault is ready
verifying we have vault installed
about to run: /root/.jx/plugins/bin/vault-1.8.3 version
Vault v1.8.3 (73e85c3c21dfd1e835ded0053f08e3bd73a24ad6)
verifying we can connect to vault...
about to run: /root/.jx/plugins/bin/vault-1.8.3 kv list secret
Keys
----
accounts/
dockerrepo
mysql
vault is setup correctly!

managed to verify we can connect to vault
VAULT_ADDR=https://vault.jx-vault:8200 jx secret wait -n jx
waiting for the mandatory Secrets to be populated from ExternalSecrets...
jenkins-x-chartmuseum: key secret/data/jx/adminUser missing properties: password, username
jx-basic-auth-user-password: key secret/data/jx/basic/auth/user missing properties: password, key secret/data/jx/basic/auth/user/password missing properties: username
lighthouse-hmac-token: key secret/data/lighthouse/hmac missing properties: token
lighthouse-oauth-token: key secret/data/lighthouse/oauth missing properties: token
nexus: key secret/data/nexus missing properties: password
tekton-container-registry-auth: key secret/data/tekton/container/registry/auth missing properties: .dockerconfigjson
tekton-git: key secret/data/jx/pipelineUser missing properties: token, username

Failure while polling the secret

I got this error from external-secret when running on EKS 1.21

"payload":{"response":{"statusCode":500,"body":{"errors":["claim \"iss\" is invalid"]}}},"msg":"failure while polling the secret jx/nexus"}

I guess we can fix this with this article

https://particule.io/en/blog/vault-1.21/

Terraform init failining due to local-exec error

After running terraform init most of the provisioning works, and then it errors with the following:

module.eks-jx.module.cluster.null_resource.kubeconfig: Creating...
module.eks-jx.module.cluster.null_resource.kubeconfig: Provisioning with 'local-exec'...
module.eks-jx.module.cluster.null_resource.kubeconfig (local-exec): Executing: ["/bin/bash" "-c" "aws eks update-kubeconfig --name tf-jx-bold-pup --region=us-west-2"]
╷
│ Error: local-exec provisioner error
│
│   with module.eks-jx.module.cluster.null_resource.kubeconfig,
│   on .terraform\modules\eks-jx\modules\cluster\main.tf line 150, in resource "null_resource" "kubeconfig":
│  150:   provisioner "local-exec" {
│
│ Error running command 'aws eks update-kubeconfig --name tf-jx-bold-pup
│ --region=us-west-2': exec: "/bin/bash": file does not exist. Output:

Sema Reaction: 🛠️ This code needs a fix

Access VPC outputs from root module

When creating additional resources to exist alongside the jx-provisioned resources, it's often necessary to access VPC details such as subnet IDs. It would be great to add outputs to the eks-jx and eks-jx.cluster modules to be able to access the VPC module outputs from the root module via module.eks-jx.vpc.

Fresh install to EKS fails with error waiting for KMS Key

│ Error: error waiting for KMS Key (d31a6a68-1850-48c3-bd36-ee50363916e7) policy propagation: timeout while waiting for state to become 'TRUE' (last state: 'FALSE', timeout: 5m0s)

also EC2 instances are up and running, but they are not registered to k8s:

kubectl get nodes                
No resources found

used versions:

Initializing provider plugins...
- Reusing previous version of hashicorp/kubernetes from the dependency lock file
- Reusing previous version of hashicorp/null from the dependency lock file
- Reusing previous version of terraform-aws-modules/http from the dependency lock file
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of hashicorp/cloudinit from the dependency lock file
- Reusing previous version of hashicorp/helm from the dependency lock file
- Reusing previous version of hashicorp/template from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of hashicorp/local from the dependency lock file
- Using previously-installed hashicorp/null v3.1.1
- Using previously-installed hashicorp/helm v2.6.0
- Using previously-installed hashicorp/template v2.2.0
- Using previously-installed hashicorp/local v2.2.3
- Using previously-installed hashicorp/aws v4.25.0
- Using previously-installed hashicorp/kubernetes v2.12.1
- Using previously-installed terraform-aws-modules/http v2.4.1
- Using previously-installed hashicorp/random v3.3.2
- Using previously-installed hashicorp/cloudinit v2.2.0

Terraform has been successfully initialized!

Fresh install fails

I followed the readme with fresh repos and the installation failed. I'm going to include details about everything I did in hopes we can fix this template. I really want jx3 to take off but the adoption of jx3 is totally dependent on these templates working out of the box. I'm going to put in some work and make a PR to fix the easy things I found but I need help with the secrets population issue at the end.

used the template links to create new repos
added the my bot account as a collaborator
made this single commit (2 file changes) to the infrastructure repo

4. exported the following env vars

export TF_VAR_jx_bot_token=<REDACTED>
export AWS_PROFILE=dev_root

my ~/.aws/credentials file looks like this:

[default]
aws_access_key_id = <REDACTED>
aws_secret_access_key = <REDACTED>

[dev_root]
role_arn = arn:aws:iam::<REDACTED>:role/OrganizationAccountAccessRole
source_profile = default

ran terraform init and received this error

removed the ref to fix

re-ran terraform init and received this error

ran terraform init -upgrade to fix
ran the code and it passed:

terraform init
terraform plan
terraform apply

I tailed the logs with jx admin logs and saw this error at the end. Random thought: Is there some additional step not outlined in the README I need to perform to populate those secrets manually or should they be populated automatically?


saved docs/releases.yaml
saved docs/README.md
jx gitops scheduler
jx gitops hash --pod-spec --kind Deployment -s config-root/namespaces/jx/lighthouse-config/config-cm.yaml -s config-root/namespaces/jx/lighthouse-config/plugins-cm.yaml -d config-root/namespaces/jx/lighthouse
jx gitops label --dir config-root/cluster                   gitops.jenkins-x.io/pipeline=cluster
jx gitops label --dir config-root/customresourcedefinitions gitops.jenkins-x.io/pipeline=customresourcedefinitions
jx gitops label --dir config-root/namespaces                gitops.jenkins-x.io/pipeline=namespaces
jx gitops annotate --dir config-root --selector app=pusher-wave kapp.k14s.io/change-group=apps.jenkins-x.io/pusher-wave
jx gitops annotate --dir config-root --selector app.kubernetes.io/name=ingress-nginx kapp.k14s.io/change-group=apps.jenkins-x.io/ingress-nginx
jx gitops label --dir config-root/cluster --kind=Namespace team=jx
jx gitops annotate --dir  config-root/namespaces --kind Deployment --selector app=pusher-wave --invert-selector wave.pusher.com/update-on-config-change=true
jx gitops git setup
found git user.name qube-bot from requirements
found git user.email  from requirements
setup git user  email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: qube-bot email: 
git add --all
git commit -m "chore: regenerated" -m "/pipeline cancel"
[main dcd6737] chore: regenerated
 17 files changed, 18 insertions(+), 18 deletions(-)
make[1]: Leaving directory '/workspace/source'
make regen-phase-3
make[1]: Entering directory '/workspace/source'
Already up to date.
To https://github.com/mrmarcsmith/jenkins-x-dev-cluster.git
   ba3cbc2..dcd6737  main -> main
VAULT_ADDR=https://vault.jx-vault:8200 VAULT_NAMESPACE=jx-vault jx secret populate --secret-namespace jx-vault
waiting for vault pod vault-0 in namespace jx-vault to be ready...
pod vault-0 in namespace jx-vault is ready
verifying we have vault installed
about to run: /root/.jx/plugins/bin/vault-1.6.1 version
Vault v1.6.1 (6d2db3f033e02e70202bef9ec896360062b88b03)
verifying we can connect to vault...
about to run: /root/.jx/plugins/bin/vault-1.6.1 kv list secret
Keys
----
accounts/
dockerrepo
mysql
vault is setup correctly!

managed to verify we can connect to vault
VAULT_ADDR=https://vault.jx-vault:8200 jx secret wait -n jx
waiting for the mandatory Secrets to be populated from ExternalSecrets...
jenkins-x-chartmuseum: key secret/data/jx/adminUser missing properties: password, username
jx-basic-auth-user-password: key secret/data/jx/basic/auth/user missing properties: password, key secret/data/jx/basic/auth/user/password missing properties: username
lighthouse-hmac-token: key secret/data/lighthouse/hmac missing properties: token
lighthouse-oauth-token: key secret/data/lighthouse/oauth missing properties: token
nexus: key secret/data/nexus missing properties: password
tekton-container-registry-auth: key secret/data/tekton/container/registry/auth missing properties: .dockerconfigjson
tekton-git: key secret/data/jx/pipelineUser missing properties: token, username

ran jx ui and gathered these relevant error messages

ran kubectl get pods --all-namespaces and noticed these failed containers

ran kubectl logs jx-preview-gc-jobs-27197690-6kjcs output only this:

WARNING: could not default pipeline user/email from requirements as file does not exist: jx-requirements.yml
error: creating git credentials: failed to load the boot secret: failed to find boot secret: failed to find secret tekton-git in namespace jx or jx-git-operator: secrets "tekton-git" not found

ran kubectl describe pod jenkins-x-chartmuseum-79c9b8dcd9-vv9sx -n jx

Events:
  Type     Reason                  Age                   From                                 Message
  ----     ------                  ----                  ----                                 -------
  Normal   Scheduled               19m                   default-scheduler                    Successfully assigned jx/jenkins-x-chartmuseum-79c9b8dcd9-vv9sx to ip-10-0-1-246.ec2.internal
  Normal   SuccessfulAttachVolume  19m                   attachdetach-controller              AttachVolume.Attach succeeded for volume "pvc-27fed11e-906d-4e9e-9948-d38a7ec760e5"
  Normal   Pulling                 19m                   kubelet, ip-10-0-1-246.ec2.internal  Pulling image "chartmuseum/chartmuseum:v0.12.0"
  Normal   Pulled                  19m                   kubelet, ip-10-0-1-246.ec2.internal  Successfully pulled image "chartmuseum/chartmuseum:v0.12.0" in 2.599439293s
  Warning  Failed                  17m (x12 over 19m)    kubelet, ip-10-0-1-246.ec2.internal  Error: secret "jenkins-x-chartmuseum" not found
  Normal   Pulled                  4m24s (x70 over 19m)  kubelet, ip-10-0-1-246.ec2.internal  Container image "chartmuseum/chartmuseum:v0.12.0" already present on machine

ran kubectl describe pod lighthouse-foghorn-86b84cb46c-dkrzm -n jx

Events:
  Type     Reason     Age                 From                                 Message
  ----     ------     ----                ----                                 -------
  Normal   Scheduled  21m                 default-scheduler                    Successfully assigned jx/lighthouse-foghorn-86b84cb46c-dkrzm to ip-10-0-3-201.ec2.internal
  Normal   Pulling    21m                 kubelet, ip-10-0-3-201.ec2.internal  Pulling image "ghcr.io/jenkins-x/lighthouse-foghorn:1.1.51"
  Normal   Pulled     21m                 kubelet, ip-10-0-3-201.ec2.internal  Successfully pulled image "ghcr.io/jenkins-x/lighthouse-foghorn:1.1.51" in 3.272873027s
  Warning  Failed     19m (x12 over 21m)  kubelet, ip-10-0-3-201.ec2.internal  Error: secret "lighthouse-oauth-token" not found
  Normal   Pulled     84s (x94 over 21m)  kubelet, ip-10-0-3-201.ec2.internal  Container image "ghcr.io/jenkins-x/lighthouse-foghorn:1.1.51" already present on machine

Error: failed to install CRD crds/khcheck.yaml: resource mapping not found for name: "khchecks.comcast.github.io" namespace: "" from "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1" ensure CRDs are installed first

Getting below error while installing it on jenkins with secrets manager. Though to skip kuberhealthy but it gives other error from kuberhealthy

Initial error

Error: failed to install CRD crds/khcheck.yaml: resource mapping not found for name: "khchecks.comcast.github.io" namespace: "" from "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
│ ensure CRDs are installed first

After disabling kuberhealthy with install_kuberhealthy = false getting below error.

error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-bot-token-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-events-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
error validating "config-root/namespaces/jx/jx-kh-check-health-checks-jx/jx-webhook-kuberhealthycheck.yaml": error validating data: ValidationError(KuberhealthyCheck.spec.podSpec.containers[0]): unknown field "restartPolicy" in io.github.comcast.v1.KuberhealthyCheck.spec.podSpec.containers; if you choose to ignore these errors, turn validation off with --validate=false
make[1]: *** [versionStream/src/Makefile.mk:322: kubectl-apply] Error 1
make[1]: Leaving directory '/workspace/source'
error: failed to regenerate: failed to regenerate phase 1: failed to run 'make regen-phase-1 NEW_CLUSTER=false' command in directory '.', output: ''
make: *** [versionStream/src/Makefile.mk:269: regen-check] Error 1

main.tf
module "eks-jx" {
  source               = "github.com/jenkins-x/terraform-aws-eks-jx?ref=v1.21.0"
  cluster_name         = data.aws_eks_cluster.cluster.id
  region               = var.region
  is_jx2               = false
  jx_git_url           = var.jx_git_url
  jx_bot_username      = var.jx_bot_username
  jx_bot_token         = var.jx_bot_token
  force_destroy        = var.force_destroy
  nginx_chart_version  = var.nginx_chart_version
  install_kuberhealthy = false
  create_autoscaler_role = false
  use_vault = false
  use_asm  = true
  create_asm_role = true
  create_eks = false
  create_vpc  = false
  cluster_version = "1.23"
  profile = "eks"
}

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.