4 ms·

Well done! Having user-challenges with kubefor.ge. Clicked "Deployment" and then tried "Create metadata node" but it errors: Missing config in qA_PQ-QAe8tzns

• DazWilkin 1y ago
  Same behavior when I run the container locally. Issues with `get.kubefor.ge/latest`: Manifest does not match provided manifest digest sha256:a4d6b4a9513289be1c1349afff46f7c87a5ac8513cbd8b66de350f26442d14bf Works with: ghcr.io/kubenote/kubeforge:latest get.kubefor.ge@sha256:a4d6b4a9513289be1c1349afff46f7c87a5ac8513cbd8b66de350f26442d14bf
• rakeda 1y ago
  Thank you! I'll double check the schema objects for metadata node, most likely some issues with how I have it defined. For the overlapping nodes, I'll also throw an issue for both of those in GH :) Did you like anything in particular or have a feature in mind that would make this better to you? --- edit --- For the metadata node warning, it was stating that the node is created but does not have values inside of it. --- edit 2 --- resolved the get.kubefor.ge/latest issue with: https://github.com/kubenote/KubeForge/issues/1 https://github.com/kubenote/KubeForge/issues/1 and removed undefined + improved warnings with: https://github.com/kubenote/KubeForge/issues/2 https://github.com/kubenote/KubeForge/issues/2