Skip to content
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

Make the registry explicit with the obsidiandynamics/kafdrop:latest image #91

Merged
merged 2 commits into from
Aug 1, 2023
Merged

Make the registry explicit with the obsidiandynamics/kafdrop:latest image #91

merged 2 commits into from
Aug 1, 2023

Commits on Aug 1, 2023

  1. Make the registry explicit with the obsidiandynamics/kafdrop:latest i… 

    …mage

Don't just assume that `obsidiandynamics/kafdrop:latest` always points
to docker.io automatically. Be explicit.

Tested with:

    podman pull docker.io/obsidiandynamics/kafdrop:latest
    Trying to pull docker.io/obsidiandynamics/kafdrop:latest...
    Getting image source signatures
    Copying blob 86fbbbe1ee3f [=>------------------------------------] 10.3MiB / 172.0MiB
    ...

The reason this is needed is that when we install certain operators from
an IIB (Image Index Bundle), we also need to whitelist which registries
a machine is allowed to connect to and making this explicit makes this
work in a more obvious manner.
    @mbaldessari
    mbaldessari committed Aug 1, 2023
    Configuration menu
    Copy the full SHA
    14dbbb7 View commit details
    Browse the repository at this point in the history

  2. Merge remote-tracking branch 'upstream/main' into explicit-image

    @mbaldessari
    mbaldessari committed Aug 1, 2023
    Configuration menu
    Copy the full SHA
    a26e981 View commit details
    Browse the repository at this point in the history