Git Product home page Git Product logo

Comments (6)

macobo avatar macobo commented on July 23, 2024 1

To fix, change clickhouseOperator.namespace: "main-tools-staging" in values.yaml

cc @fuziontech @tiina303 - having this option still seems slightly weird. Perhaps it should just default to the same namespace?

from charts-clickhouse.

taobojlen avatar taobojlen commented on July 23, 2024 1

Thanks @tiina303 -- we'll leave in clickhouseOperator.namespace for now then!

Re: the wrapped config values, it's an internal convention to "wrap" charts as dependencies in custom charts of our own. It turns out thaat using posthog instead of posthog-clickhouse for this actually fixes the problems (so our Chart.yaml has name: posthog and all values are under the posthog key).

Closing this; thanks for your help!

from charts-clickhouse.

fuziontech avatar fuziontech commented on July 23, 2024 1

cc @fuziontech @tiina303 - having this option still seems slightly weird. Perhaps it should just default to the same namespace?

Yeah this is for legacy compatibility and can be nuked now. #79 addresses it

from charts-clickhouse.

taobojlen avatar taobojlen commented on July 23, 2024

The error still appears without setting clickhouseOperator.namespace (I actually only changed that in an attempt to work around the bug). Sorry, could've been clearer about that!

from charts-clickhouse.

tiina303 avatar tiina303 commented on July 23, 2024

The error still appears without setting clickhouseOperator.namespace (I actually only changed that in an attempt to work around the bug). Sorry, could've been clearer about that!

Sorry this is inconvenient. Currently you need to set that value or have "posthog" namespace. I agree that this is confusing and annoying that we need to define it, I'll look into removing that.

Why you're running into the error with your initial values that you provided: I'm not sure how your values are used as normally they would be at the top level, i.e.
instead of

posthog-clickhouse:
  cloud: "gcp"
  ...

you'd have

cloud: "gcp"
...

from charts-clickhouse.

tiina303 avatar tiina303 commented on July 23, 2024

Looked into the clickhouseOperator.namespace and by default it would otherwise install into kube-system namespace (https://github.com/Altinity/clickhouse-operator/blob/master/docs/operator_installation_details.md), however I think it's better if we keep all Posthog things in the same namespace and I couldn't find a way to use the current namespace.

from charts-clickhouse.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.