Open junji2 opened 3 years ago
╰─$ kubectl get filterdeployments.wasme.io --all-namespaces -o yaml
apiVersion: v1
items:
- apiVersion: wasme.io/v1
kind: FilterDeployment
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"wasme.io/v1","kind":"FilterDeployment","metadata":{"annotations":{},"name":"myfilter","namespace":"nginx"},"spec":{"deployment":{"istio":{"kind":"Deployment"}},"filter":{"image":"webassemblyhub.io/qiujj/header_test:v0.2"}}}
creationTimestamp: "2021-06-19T05:57:03Z"
generation: 1
managedFields:
- apiVersion: wasme.io/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:kubectl.kubernetes.io/last-applied-configuration: {}
f:spec:
.: {}
f:deployment:
.: {}
f:istio:
.: {}
f:kind: {}
f:filter:
.: {}
f:image: {}
manager: kubectl-client-side-apply
operation: Update
time: "2021-06-19T05:57:03Z"
name: myfilter
namespace: nginx
resourceVersion: "8302772"
uid: a6963834-123d-4cb5-99fb-4d23685bd903
spec:
deployment:
istio:
kind: Deployment
filter:
image: webassemblyhub.io/qiujj/header_test:v0.2
kind: List
metadata:
resourceVersion: ""
selfLink: ""
istio version 1.9.3 kubernetes version 1.20.4 operator version quay.io/solo-io/wasme:0.0.32
filterDeployment.yaml:
after I run the command:
wasme operate log:
it stopped at 'updated workload sidecar annotations' and did not connitue to 'created Istio EnvoyFilter resource '
Have you ever encountered this situation