env-config | Configuring your unix work environment

You doesn't seem to have a Node that match your affinity requirement.

Remove the affinity requirement on your PersistentVolume:

Remove this part:

I could not comment on your question because of my reputation. If it is possible for your case, you can use the config map as a file. I think Reading the property file in your code is easier.

https://kubernetes.io/docs/concepts/configuration/configmap/#using-configmaps-as-files-from-a-pod

In the deployment yaml env-config is referred as configMapKeyRef in all the places. Hence kubernetes is expecting POSTGRESS_DATABASE to be present in env-config configMap. You can refer to a secret which contains key POSTGRESS_DATABASE key using secretKeyRef.

Here is an example.

According to this modify the ingress like following

So you kind of got things a little weird. What you have there is a config map with one key named env-config.yaml, the value of which is a string containing YAML data for a config map with a bunch of keys including URL. I'm guessing you tried using kubectl create cm --from-file instead of kubectl apply -f?

Are you using same tsconfig file as in the project? If not make sure to use define same path variable in your tsconfig file.

Source tsconfig file: https://github.com/Jaspero/fireshop/blob/1d893923dd2c4016b4510b84dde7dfe60796306b/client/tsconfig.json

If your instance is running in your default zone "us-central1-b", you can simply do gcloud compute instances describe However, if your instance is not running in the defautl zone you have to provide the zone as well so you will do:

gcloud compute instances describe my-instance-1 --zone us-east4-a

If you look at the output: "The resource 'projects/my-project/zones/us-central1-b/instances/my-instance-1'" You can clearly see it's looking in your default zone us-central1-b

I'm either misunderstanding your use case or you're missing an important point about including the file at build time.

The point of having a JSON configuration file, if I understand correctly, is for system administrators to be able to configure the application at any time. However, injecting the JSON file into the application at build time means it will baked into the executable binary forever. The only way for the changes in the JSON file to take place is to rebuild the application again.

If that is what you want, I would suggest to simplify your life and make the configuration a header file that you can simply include in your source code (instead of JSON) similar to this:

config.h

As you point out, you can re-use the ConfigMap so that other parts of your chart can easily re-use the same environment variables. How useful this is can depend on how many variables you have and how many places they are used in.

A ConfigMap is also available as an Object in the cluster that other Pods can make use of, including ones that are not part of your chart. This could mean your configmap getting referenced by other apps getting installed in the same cluster, or it could be that you choose to publish your chart and then it might get packaged as a dependency within another chart. If your chart is to be used as a dependency in another chart then it makes things a bit easier/cleaner for the chart that is building on top of yours to reference parts of your configuration from a ConfigMap. So the usefulness can also depend on how you intend your chart to be used. The official charts use a lot of ConfigMaps but they do sometimes use environment variables directly and they use ConfigMaps in a variety of ways for different purposes.