Skip to content

Pull and parse parent devfile from Kubernetes CRD in library #355

Description

@yangcao77

Currently devfile library can only parse parent devfile if uri is specified.

This issue is to support Kubernetes CRD defined under parent.
(Question: should be with type DevWorkspaceTemplate or DevWorkspace ??)

Needs to get KubeConfig and creates Kubernetes client, and access the Kubernetes CRD from that client.

The parent devfile should be parsed & override & merge into the flattened devfile.

Activity

  1. added
    area/libraryCommon devfile library for interacting with devfiles
    on Feb 23, 2021
  2. maysunfaisal commented on Mar 11, 2021

    @maysunfaisal
    Member

    Before starting we should check with the devworkspace operator repo and if they have logic in place for this issue already and needs consolidation..

  3. yangcao77 commented on Mar 17, 2021

    @yangcao77
    ContributorAuthor

    Talked with Angel, devworkspace operator now gets plugin from CRD via the same mechanism. They are going to help port over the common functions(get KubeConfig and creates Kubernetes client, and access the Kubernetes CRD from that client) & tests into library

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/libraryCommon devfile library for interacting with devfiles

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions