Layer7 Gateway Operator is not removing API when bundled is deleted from "connected" Git repository .
search cancel

Layer7 Gateway Operator is not removing API when bundled is deleted from "connected" Git repository .

book

Article ID: 423970

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

we are testing the Layer7 Gateway Operator (https://github.com/CAAPIM/layer7-operator) deployment to manage our Layer7 API gateway in Kubernetes environment. We connected a Git repository for our bundles files (such as API) definitions. Almost everything works as expected: If we add a file (bundle with API definition) to the repository, the operator updates the gateway and deploys the new API there.

What does not work is: If we delete a (bundle) file from the Git repository, the operator does not delete/undeploy the respective API in the gateway even though (when watching the operator's logs), it seems that the operator "sees" the change and starts a sync.

Is there maybe a setting that we miss to enable delete operations?

Environment

11.1

Resolution

There is delete support in v1.2.2 - it is disabled by default and recommended with ephemeral gateways and an L7StateStore, Setting "includeEfs=true" enabled the deletion as expected on top of the below settings for example

apiVersion: security.brcmlabs.com/v1
kind: Gateway
metadata:
  name: ssg
spec:
  app:
    repositoryReferenceDelete:
      enabled: false
      includeEfs: false
      reconcileReferences: false
      reconcileDirectoryChanges: true