Skip to content

Bytewax Image Pull Secrets Wrong Format #3546

@adamschmidt

Description

@adamschmidt

Expected Behavior

Bytewax materializer uses a correctly configured list of image secrets to pull the job container on execution

Current Behavior

Current configuration is a list of strings. Container scheduling fails to start because of an invalid generated job spec.

Steps to reproduce

Configure Bytewax materialization engine with image pull secrets as list of strings, and run materialization. It'll fail.

Specifications

  • Version: 0.30.0
  • Platform: Linux & EKS
  • Subsystem: Python, Feast with Bytewax option enabled

Possible Solution

The Bytewax materialization engine config needs to be configured with a List[dict] per Kubernetes configuration requirements. This will correctly schedule the materialization job and use the secrets to pull the job container from the registry.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions