@@ -29,7 +29,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        component: [ feature-server, feature-server-java, feature-transformation-server, feast-helm-operator, feast-operator ]
+        component: [ feature-server, feature-server-java, feature-transformation-server, feast-operator ]
     env:
       MAVEN_CACHE: gs://feast-templocation-kf-feast/.m2.2020-08-19.tar
       REGISTRY: quay.io/feastdev
 
@@ -66,7 +66,6 @@ module.exports = {
                     "CHANGELOG.md",
                     "java/pom.xml",
                     "infra/charts/**/*.*",
-                    "infra/feast-helm-operator/**/*",
                     "infra/feast-operator/**/*",
                     "ui/package.json",
                     "sdk/python/feast/infra/feature_servers/multicloud/requirements.txt",
 
@@ -528,18 +528,6 @@ build-feature-server-java-docker:
 		-t $(REGISTRY)/feature-server-java:$(VERSION) \
 		-f java/infra/docker/feature-server/Dockerfile --load .
 
-push-feast-helm-operator-docker:
-	cd infra/feast-helm-operator && \
-	IMAGE_TAG_BASE=$(REGISTRY)/feast-helm-operator \
-	VERSION=$(VERSION) \
-	$(MAKE) docker-push
-
-build-feast-helm-operator-docker:
-	cd infra/feast-helm-operator && \
-	IMAGE_TAG_BASE=$(REGISTRY)/feast-helm-operator \
-	VERSION=$(VERSION) \
-	$(MAKE) docker-build
-
 push-feast-operator-docker:
 	cd infra/feast-operator && \
 	IMAGE_TAG_BASE=$(REGISTRY)/feast-operator \
 
@@ -225,8 +225,6 @@ helm install feast-release feast-charts/feast-feature-server \
 
 This will deploy a single service. The service must have read access to the registry file on cloud storage and to the online store (e.g. via [podAnnotations](https://kubernetes-on-aws.readthedocs.io/en/latest/user-guide/iam-roles.html)). It will keep a copy of the registry in their memory and periodically refresh it, so expect some delays in update propagation in exchange for better performance. 
 
-> Alternatively, deploy the same helm chart with a [Kubernetes Operator](/infra/feast-helm-operator).
-
 ## 5. Using environment variables in your yaml configuration
 
 You might want to dynamically set parts of your configuration from your environment. For instance to deploy Feast to production and development with the same configuration, but a different server. Or to inject secrets without exposing them in your git repo. To do this, it is possible to use the `${ENV_VAR}` syntax in your `feature_store.yaml` file. For instance: