10000 Fails to install a chart with a pre-install hook running a job using a configmap · Issue #334 · werf/nelm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fails to install a chart with a pre-install hook running a job using a configmap #334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
ds-varian opened this issue May 21, 2025 · 1 comment
Closed
1 task done

Fails to install a chart with a pre-install hook running a job using a configmap #334

ds-varian opened this issue May 21, 2025 · 1 comment

Comments

@ds-varian
Copy link
ds-varian commented May 21, 2025 •
edited
Loading

Before proceeding

  • I didn't find a similar issue

Version

1.4.0

How to reproduce

Trying to migrate from helm to nelm and I have a problem with a helm chart.

The helm chart has a pre-install hook with a job referencing a configmap. The pods of the job fails to start because of missing configmap.

Result

Checking the logs this is what I see

Processing resources
Transforming hook resources
Transforming general resources
Validating resources
Building releasable resources
Building releasable hook resources
Building releasable general resources
Validating releasable resources
Building deployable standalone CRDs
Building deployable hook resources
Building deployable general resources
Validating deployable resources
Building deployable resource infos
Getting resource "ConfigMap/xxx-api-resource-json"
Getting resource "ConfigMap/xxx-client-resource-json"
Getting resource "Job/xxx-client-pre-install"
Getting resource "Job/xxx-pre-install"
Getting resource "ConfigMap/xxx-appsettings-json"
Getting resource "ConfigMap/xxx-extra-envs"
Server-side dry-run applying resource "Job/xxx-pre-install"
Getting resource "ConfigMap/xxx-operator-envs"
Getting resource "ConfigMap/xxx-redis-configuration"
Getting resource "ConfigMap/xxx-redis-health"
Getting resource "ConfigMap/xxx-redis-scripts"
Getting resource "Deployment/xxx"
Getting resource "HorizontalPodAutoscaler/xxx"
Getting resource "IngressRoute/xxx"
Getting resource "Middleware/xxx-forward-auth-jwt"
Getting resource "Middleware/xxx-forward-oauth"
Getting resource "Secret/xxx-bootstrap-client-secret"
Getting resource "Service/xxx-redis-headless"
Getting resource "Service/xxx-redis-master"
Getting resource "Service/xxx-redis-replicas"
Getting resource "Service/xxx-service"
Getting resource "ServiceAccount/xxx-redis"
Getting resource "StatefulSet/xxx-redis-master"
Getting resource "StatefulSet/xxx-redis-replicas"
Validating adoptable resources
Constructing new release
Constructing new deploy plan
Setting up init operations
Setting up standalone CRDs operations
Setting up pre hook resources operations
Setting up general resources operations
Setting up post hook resources operations
Setting up prev release general resources operations
Setting up finalization operations
Connecting stages
Connecting internal dependencies
Optimizing plan
Starting tracking
Executing release install plan
Create resource: ConfigMap/xxx-api-resource-json
Server-side applying resource "ConfigMap/xxx-api-resource-json"
Delete resource: ConfigMap/xxx-api-resource-json
Deleting resource "ConfigMap/xxx-api-resource-json"
Recreate resource: Job/xxx-pre-install
Deleting resource "Job/xxx-pre-install"
┌ Progress status
│ RESOURCE (→READY) STATE INFO
│ ConfigMap/xxx-api-resource-json READY
│ ConfigMap/xxx-appsettings-json WAITING
│ ConfigMap/xxx-client-resource-json WAITING
│ ConfigMap/xxx-extra-envs WAITING
│ ConfigMap/xxx-operator-envs WAITING
│ ConfigMap/xxx-redis-configuration WAITING
│ ConfigMap/xxx-redis-health WAITING
│ ConfigMap/xxx-redis-scripts WAITING
│ Deployment/xxx WAITING
│ HorizontalPodAutoscaler/xxx WAITING
│ IngressRoute/xxx WAITING
│ Job/xxx-client-pre-install WAITING
│ Job/xxx-pre-install WAITING
│ Middleware/xxx-forward-auth-jwt WAITING
│ Middleware/xxx-forward-oauth WAITING
│ Secret/xxx-bootstrap-client-secret WAITING
│ Service/xxx-redis-headless WAITING
│ Service/xxx-redis-master WAITING
│ Service/xxx-redis-replicas WAITING
│ Service/xxx-service WAITING
│ ServiceAccount/xxx-redis WAITING
│ StatefulSet/xxx-redis-master WAITING
│ StatefulSet/xxx-redis-replicas WAITING
│
│ RESOURCE (→ABSENT) STATE INFO
│ ConfigMap/xxx-api-resource-json ABSENT
│ ConfigMap/xxx-client-resource-json WAITING
│ Job/xxx-client-pre-install WAITING
│ Job/xxx-pre-install WAITING
│ Job/xxx-pre-install WAITING
└ Progress status

Server-side applying resource "Job/xxx-pre-install"
┌ Progress status
│ RESOURCE (→READY) STATE INFO
│ Job/xxx-pre-install WAITING Ready:0/1
│ • Pod/xxx-pre-install-ht7sk UNKNOWN Status:Init:0/1
│ ConfigMap/xxx-appsettings-json WAITING
│ ConfigMap/xxx-client-resource-json WAITING
│ ConfigMap/xxx-extra-envs WAITING
│ ConfigMap/xxx-operator-envs WAITING
│ ConfigMap/xxx-redis-configuration WAITING
│ ConfigMap/xxx-redis-health WAITING
│ ConfigMap/xxx-redis-scripts WAITING
│ Deployment/xxx WAITING
│ HorizontalPodAutoscaler/xxx WAITING
│ IngressRoute/xxx WAITING
│ Job/xxx-client-pre-install WAITING
│ Middleware/xxx-forward-auth-jwt WAITING
│ Middleware/xxx-forward-oauth WAITING
│ Secret/xxx-bootstrap-client-secret WAITING
│ Service/xxx-redis-headless WAITING
│ Service/xxx-redis-master WAITING
│ Service/xxx-redis-replicas WAITING
│ Service/xxx-service WAITING
│ ServiceAccount/xxx-redis WAITING
│ StatefulSet/xxx-redis-master WAITING
│ StatefulSet/xxx-redis-replicas WAITING
│
│ RESOURCE (→ABSENT) STATE INFO
│ ConfigMap/xxx-client-resource-json WAITING
│ Job/xxx-client-pre-install WAITING
│ Job/xxx-pre-install ABSENT
│ Job/xxx-pre-install WAITING
└ Progress status

The pod fails to start because ConfigMap does not exist xxx-api-resource-json

While waiting, I double-checked the cluster and the ConfigMap doesn't exist.

Expected result

Same configuration works fine via helm and this is the expectation also with nelm

Additional information

No response
@ds-varian ds-varian changed the title Nelm fails to install a chart with a pre-install hook using a configmap Fails to install a chart with a pre-install hook using a configmap May 21, 2025
@ds-varian ds-varian changed the title Fails to install a chart with a pre-install hook using a configmap Fails to install a chart with a pre-install hook running a job using a configmap May 22, 2025
@ilya-lesikov
Copy link
Member

Probably a duplicate. The workaround is here: #117 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ilya-lesikov @ds-varian
0