How you manage your host remotes config? #536
SombreroElGringo
started this conversation in
General
Replies: 1 comment
-
I strongly recommend going with #1. Even with K8s in place, you can host your API service within the same K8s cluster where Host pod is deployed and establish a Pod-to-Pod direct connectivity instead of routing your requests through ingress. This way your API will always be available without worrying about the down time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I would like to understand what options and how others manage their remote hosts configuration.
Let's say we have a host application whose main role is to be a simple layout sharing a header and its content is where we inject our remote applications. Depending on the path we are on, we inject a specific remote application via a dynamic import (injectScrip or etc.).
Here is the setup. Let's say we are asked to update or disable a remote application without redeploying anything. We should achieve this just by updating our configuration. How would you do that?
Here are some ideas/tests I did:
Fetch an API to get the remote apps we want to load. In the s schéma, we have an prop to know if the remote app is active, disabled or in maintenance. (Very flexible but if the API is down we can't figure out which remote to load)
If the host is running in Kubernetes, we can create a json file with all our remote configurations and use a ConfigMap. When we update the ConfigMap it will quickly reload the host pod with this new config. (Less flexible but less risk of losing access to our config)
Combination of API and ConfigMap. We make a daily backup of the API response in the ConfigMap so if the API is down we can just use the ConfigMap.
Beta Was this translation helpful? Give feedback.
All reactions