Skip to content

Add ODG controller #411

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.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add ODG controller #411

wants to merge 1 commit into from

Conversation

zkdev
Copy link
Member

@zkdev zkdev commented Apr 8, 2025

Reconciles ODG resources in mODG-root cluster and creates ODG-Extension resources (via gardener-resource-manager).

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:


@zkdev zkdev requested a review from a team as a code owner April 8, 2025 08:30
@ocm-ci-robot-0 ocm-ci-robot-0 added reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/ok-to-test and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Apr 8, 2025
import odg_operator.odg_model as odgm


ci.log.configure_default_logging()
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would prefer to new code to avoid dependencies to ci.* packages. esp. sth. basic like logging we should rather define locally (esp. considering that we might see a different logging infrastructure for ODG - e.g. conveying logs to some service, rather than (only) printing to stdout).

@zkdev zkdev force-pushed the zkdev-odg-controller branch 3 times, most recently from 218d87a to 484d21a Compare May 2, 2025 13:45
logger.info(f'{event["type"]} "{odg_name}" in "{metadata["namespace"]}"')

requested_extension_definitions = [
find_extension_definition(
Copy link
Member

Choose a reason for hiding this comment

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

In order to support external extension definitions as well, we have to specify a fallback here in case the extension is not find in "our" definitions.

Copy link
Member Author

Choose a reason for hiding this comment

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

so we would need something like:

dependencies:
- name: custom-extension
  type: custom
  component_name: my-custom.component.foo
  component_version: 0.1.0
  artefact_name: my-artefact
- name: delivery-service
  type: supported

wdyt?

@zkdev zkdev force-pushed the zkdev-odg-controller branch 3 times, most recently from 1f189d5 to 1fb1b1a Compare May 7, 2025 08:03
Reconciles ODG resources in mODG-root cluster and creates ODG-Extension
resources (via gardener-resource-manager).
@zkdev zkdev force-pushed the zkdev-odg-controller branch from 1fb1b1a to 9b20804 Compare May 7, 2025 12:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants