Referencing External Files in a values.yaml configMap

Snap E Tom

6/21/24, 10:04 AM

In the data: section of my values.yaml, I have a schema that gets a bit unwieldy. This schema is used in a configMap. Later, a Spark job uses this configMap to create tables. This file is getting big, so I am trying to split off each schema definition in its own file:

"schemas": {
        "core": {
            "tables": {
                "books": { "$ref": "../schemas/core/books.json"},
                "trucks": {"$ref": "../schemas/core/trucks.json"},
                "lanes": {"$ref": "../schemas/core/lanes.json"}
            }
        },
        "dashboards": {
             "tables": {
                 ...

The problem is $ref pointing to an outside file, doesn't work. The tables specified with $ref do not work. If I substitute the values with explicit JSON objects, it does. Does the $ref keyword, valid in JSON, work for this purpose? If not, what is the best way to approach referencing external files?

My directory structure:

// top
/provisioning
    /schemas
       /core
          ..books.json
          ..trucks.json
          ..lanes.json
       /dashboards
    /templates
       /values.yaml

Is what I'm doing possible? Are my directories and files set up correctly to do this?

0 + 0

helm

Elon Musk

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

EN: Referencing External Files in a values.yaml configMap

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.