Score:0

deploy nginx-ingress with large nginx config

cl flag

I have an nginx-ingress controller that I has multiple hosts connected to it. I have built the config as a ConfigMap, but when I attempt to deploy it, I keep getting and error message that says the config is to large. If creating a ConfigMap is not an option then, what options do I have to deploy the ingress with my large nginx config?

The ConfigMap "nginx-conf" is invalid: metadata.annotations: Too long: must have at most 262144 bytes

in flag
I presume this is a dupe of [your other question](https://serverfault.com/questions/1117702/build-custom-nginx-ingress-image)?
Score:0
tr flag

This is because ConfigMaps have a maximum size limit of 256KB, and your nginx config is larger than this limit.

Use a separate ConfigMap for each part of the nginx config. If splitting up the nginx config into multiple key-value pairs is not practical, you can create multiple ConfigMaps, each containing a different part of the nginx config. You can then reference these ConfigMaps in your deployment manifest, and they will be combined to form the complete nginx config when the nginx-ingress controller is deployed.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.