Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DbtTaskGroup - Kubernetes Execution with RenderConfig #943

Open
harshag7dm opened this issue May 7, 2024 · 3 comments
Open

DbtTaskGroup - Kubernetes Execution with RenderConfig #943

harshag7dm opened this issue May 7, 2024 · 3 comments
Assignees
Labels
area:execution Related to the execution environment/mode, like Docker, Kubernetes, Local, VirtualEnv, etc area:rendering Related to rendering, like Jinja, Airflow tasks, etc epic-assigned execution:kubernetes Related to Kubernetes execution environment triage-needed Items need to be reviewed / assigned to milestone
Milestone

Comments

@harshag7dm
Copy link

When I use Kubernetes Execution in DbtTaskGroup and try to filter out the Models using tag, it doesn't work. There is no Kubernetes pod being run.
If I remove the RenderConfig, then all the models are run?
Is this a bug or am I missing something?

Copy link

dosubot bot commented May 7, 2024

It sounds like you're encountering an issue where using RenderConfig with DbtTaskGroup in a Kubernetes environment doesn't trigger the execution of pods when filtering models by tag. This could be due to a configuration issue or a more complex problem within the interaction of DbtTaskGroup, RenderConfig, and Kubernetes Execution.

To address this, ensure that your DbtTaskGroup is correctly configured to include the tag filter in its arguments for dbt tasks. The RenderConfig should be set up properly with the necessary class arguments and Kubernetes-specific configurations. For detailed guidance, refer to the documentation on configuring RenderConfig and Kubernetes execution in the Cosmos repository.

Additionally, check for any recent changes or updates in the Cosmos repository that might affect this functionality. Specifically, look into the changelog for updates related to Docker and Kubernetes operators, as these could impact how DbtTaskGroup operates with Kubernetes Execution.

If the issue persists, examining the logs or error messages for any clues on why the Kubernetes pod is not being initiated could provide further insights. The DbtTestKubernetesOperator class, for example, includes methods designed to handle warnings and extract log issues, which might reveal underlying problems.

If you can provide more details about your configuration and any specific error messages you're encountering, it would help in diagnosing and resolving the issue more effectively.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@dosubot dosubot bot added area:execution Related to the execution environment/mode, like Docker, Kubernetes, Local, VirtualEnv, etc area:rendering Related to rendering, like Jinja, Airflow tasks, etc execution:kubernetes Related to Kubernetes execution environment labels May 7, 2024
@tatiana
Copy link
Collaborator

tatiana commented May 8, 2024

@harshag7dm please, could you confirm which version of Cosmos you've tried, with which DAG?

@tatiana
Copy link
Collaborator

tatiana commented May 17, 2024

@tatiana tatiana added this to the 1.5.0 milestone May 17, 2024
@tatiana tatiana added the triage-needed Items need to be reviewed / assigned to milestone label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:execution Related to the execution environment/mode, like Docker, Kubernetes, Local, VirtualEnv, etc area:rendering Related to rendering, like Jinja, Airflow tasks, etc epic-assigned execution:kubernetes Related to Kubernetes execution environment triage-needed Items need to be reviewed / assigned to milestone
Projects
None yet
Development

No branches or pull requests

3 participants