Skip to content

Add satellite flavor for downstream deployments#628

Draft
zjhuntin wants to merge 1 commit into
theforeman:masterfrom
zjhuntin:satellite-flavor
Draft

Add satellite flavor for downstream deployments#628
zjhuntin wants to merge 1 commit into
theforeman:masterfrom
zjhuntin:satellite-flavor

Conversation

@zjhuntin

@zjhuntin zjhuntin commented Jul 7, 2026

Copy link
Copy Markdown

Summary

  • Adds a satellite flavor (src/vars/flavors/satellite.yml) with the feature set for Satellite deployments
  • Enables: foreman, katello, content/{ansible,container,rpm}, hammer, remote-execution, rh-cloud, iop, theme-satellite
  • Compared to katello flavor: drops content/deb and content/python, adds features that Satellite ships by default

Details

The theme-satellite feature requires a corresponding entry in features.yaml (or features.d/) to take effect. Without one, it is silently ignored.

Usage:

foremanctl deploy --flavor satellite --initial-admin-password=changeme

Test plan

  • Deployed with --flavor satellite on a CentOS 9 VM — all features resolved, 0 failures
  • Verified foremanctl features shows correct enabled/available features
  • Verified hammer ping — all services healthy
  • CI tests pass

🤖 Generated with Claude Code

Comment thread src/vars/flavors/satellite.yml Outdated
Comment thread src/vars/flavors/satellite.yml Outdated
Comment on lines +3 to +4
- foreman
- katello

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

foreman-proxy feature can be added to this list

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as with hammer, I think that is something people should be actively opt in for?
content distribution to external proxies works without the feature, so in many architectures it won't be needed

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for now I do not have foreman-proxy enabled by default.

Comment thread src/vars/flavors/satellite.yml Outdated
@zjhuntin zjhuntin force-pushed the satellite-flavor branch 3 times, most recently from c40b500 to 91b2b95 Compare July 7, 2026 14:46
The satellite flavor provides a feature set matching what RPM-based
Satellite ships by default, enabling proper downstream test coverage
with foremanctl.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@zjhuntin zjhuntin force-pushed the satellite-flavor branch from 91b2b95 to 08d9a70 Compare July 7, 2026 15:50
@zjhuntin

zjhuntin commented Jul 7, 2026

Copy link
Copy Markdown
Author

tested the most recent version and that worked as well 😄

help: Base flavor to use in this deployment.
choices:
- katello
- satellite

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO a Satellite user should not be able to select Katello, and a Katello user not Satellite

But we don't need to solve this right now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants