Verify that Marketplace CRDs are present

If d8 k get applications returns an error that the resource type doesn’t exist, the Marketplace CRDs may not be installed. To check, run the following command:

d8 k get crd | grep -E 'application|package'

Expected output:

applicationpackages.deckhouse.io                     2026-02-10T14:54:41Z
applicationpackageversions.deckhouse.io              2026-02-10T14:54:41Z
applications.deckhouse.io                            2026-02-10T14:54:41Z
packagerepositories.deckhouse.io                     2026-02-10T14:54:41Z
packagerepositoryoperations.deckhouse.io             2026-02-10T14:54:41Z

If any CRDs are missing, contact your cluster administrator. Marketplace requires DP version 1.76 or later.

Read the application summary

The quickest way to understand why an application is not working is to check status.summary. Use the following command:

d8 k get applications -n <NAMESPACE> <APPLICATION_NAME> -o yaml | grep -A5 'summary:'

Example output:

summary:
  state: Updating
  message: "Update is waiting for dependent modules to converge; previous version is still serving"
  tip: "Wait — the previous version is still working. The update will continue automatically once dependent modules converge."
  • state — current high-level state of the application: Pending, Failed, Updating, Ready, Degraded, Suspended, or Deleting.
  • message — explains why the application is in this state.
  • tip — what to do to resolve the issue or what DP is waiting for.

Read individual conditions

To get a more detailed view of the application state, use the following command:

d8 k get applications -n <NAMESPACE> <APPLICATION_NAME> \
  -o jsonpath='{range .status.conditions[*]}{.type}: {.status} ({.reason}) - {.message}{"\n"}{end}'

Example output for an update that is waiting:

Installed: True (Installed) -
UpdateInstalled: False (Pending) - waiting for processing
ConfigurationApplied: True (ConfigurationApplied) -
Managed: True (Managed) -
Scaled: True (Scaled) -
Ready: True (Ready) -

In this example, Installed=True means that the application is running the previously installed version, and UpdateInstalled=False with the Pending reason means that the update is waiting, for example, for the modules the application depends on. The installed version is shown in the status.currentVersion.version field.

Check the DP logs

If the conditions don’t provide enough detail, ask the cluster administrator to check the DP log. The log is available only in the d8-system namespace:

d8 k -n d8-system logs svc/deckhouse-leader -c deckhouse | grep '<NAMESPACE>.<APPLICATION_NAME>'

Check the application Pod logs

The objects of an application are named d8a-<APPLICATION_NAME>-<SUFFIX>. To list the Deployments and StatefulSets of the application, run the following command:

d8 k get deployments,statefulsets -n <NAMESPACE> -l packages.deckhouse.io/instance=<APPLICATION_NAME>

The Pods of these workloads have names with the same prefix. To list them, run:

d8 k get pods -n <NAMESPACE> | grep 'd8a-<APPLICATION_NAME>-'

To view logs for a specific Pod, run:

d8 k logs -n <NAMESPACE> <POD_NAME>

To view logs for a Deployment of the application, run:

d8 k logs -n <NAMESPACE> deployments/d8a-<APPLICATION_NAME>-<SUFFIX>

Common condition reasons

Reason Conditions Meaning and what to check
Pending Installed, UpdateInstalled DP is waiting to install the version, for example, until the modules from requirements.modules of the package are enabled. Ask the administrator to check these modules
RequirementsUnmet Installed The cluster doesn’t meet the package requirements. The message names the unmet requirement
DownloadFailed Installed, UpdateInstalled, ConfigurationApplied, Managed, Ready DP can’t download the package version. Ask the administrator to check the PackageRepository and access to the container registry
LoadFromFilesystemFailed Installed, UpdateInstalled, Ready DP can’t read the downloaded package. Contact the package developer
SettingsInvalid Installed, UpdateInstalled, ConfigurationApplied The settings didn’t pass validation. Check spec.settings against the settings schema of the ApplicationPackageVersion
HookInitializationFailed, HookFailed Installed, UpdateInstalled, ConfigurationApplied, Managed, Ready A hook of the package failed. The message contains the error
ManifestsApplyFailed Installed, UpdateInstalled, ConfigurationApplied, Managed, Ready DP can’t apply the manifests of the package. Check the message and the events in the namespace
ApplyingManifests UpdateInstalled, ConfigurationApplied, Managed, Ready Not an error: DP is applying the manifests
Reconciling Scaled A workload is rolling out. The message names the workload
Degraded Scaled A workload failed to roll out. Check the events and the Pods of the workload with d8 k describe
Deleting All The application is being deleted

Additional resources