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.

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

Different ingress host or different config-map #154

Open
geekette86 opened this issue Dec 20, 2022 · 2 comments
Open

Different ingress host or different config-map #154

geekette86 opened this issue Dec 20, 2022 · 2 comments

Comments

@geekette86
Copy link

Hey, i just came to know admiralty(great product) and my question is , can i sync different clusters but change the ingress host name or some config map

@geekette86 geekette86 changed the title Diffrent ingress host or diffrent configmap Different ingress host or different config-map Dec 20, 2022
@geekette86
Copy link
Author

Hello @adrienjt can i have a quick answer for this .thank you

@adrienjt
Copy link
Contributor

adrienjt commented Jul 7, 2023

Hi @geekette86, sorry for the delayed response. This isn't currently possible, but we've discussed cluster-specific pod transformations before: #96 (comment)

The concept could be generalized to other types. You'd annotate your source ingress or configmap with multicluster.admiralty.io/target-transformation: different-hostname, referring to:

kind: TargetTransformation
metadata:
  name: different-hostname
transformations:
- targetSelector: 
    region: eu
  # maybe specify the GVK here, so we can type-check the patch when the TargetTransformation is created
  patch: |
    # user can define inline strategic merge patch here

Would that work for you? Would you like to implement and contribute this design?

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

No branches or pull requests

2 participants