shvgn commented 9 months ago

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Version

v1.56

Expected Behavior

A 'Deployed' deckhouse release (deckhouserelease resource) should be created on finished installation.

Actual Behavior

Only 'Pending' deckhouse release is created whereas deckhouse Pod is up and running

Steps To Reproduce

IDK exact steps. Deckhouse update settings were applied to default values (not set). After ~2hr I noticed the 'update' was actually applied, and the release became 'Deployed'.

Additional Information

During installation, current configuration was applied. ModuleConfig/deckhouse was not specified.

apiVersion: deckhouse.io/v1
kind: InitConfiguration
deckhouse:
  imagesRepo: registry.deckhouse.io/deckhouse/ee
  registryDockerCfg: eyJhd.....
  releaseChannel: EarlyAccess

Logs

No response

konstantin-axenov commented 9 months ago

This happens only on EarlyAccess and Stable release channels because of canary releases. Deckhouse has to apply Pending release immediately if there are no releases (it means that cluster was just bootstrapped).

shvgn commented 6 months ago

7303 closed this issue, but the issue is still present. Installing 1.58.7 does not create deckhouse release in Deployed state, it is still Pending from the start.

deckhouse / deckhouse

Deckhouse installation does not have 'deployed' deckhouse release, only 'pending' one #7133