Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set MIRRORD_AGENT_IMAGE for vscode e2e and tidy actions #1495

Merged
merged 31 commits into from
Jun 4, 2023

Conversation

infiniteregrets
Copy link
Contributor

No description provided.

@infiniteregrets infiniteregrets changed the title Set MIRRORD_AGENT_IMAGE for vscode e2e Set MIRRORD_AGENT_IMAGE for vscode e2e and tidy actions Jun 2, 2023
@aviramha
Copy link
Member

aviramha commented Jun 4, 2023

qq: how did you verify it actually uses the test image?

@infiniteregrets
Copy link
Contributor Author

qq: how did you verify it actually uses the test image?

i did a simple test:

ran : MIRRORD_AGENT_IMAGE="test" KUBE_SERVICE=localhost:30000 POD_TO_SELECT=py-serv-deployment-ff89b5974-dhl2q node out/tests/runTests.js
didn't build the image beforehand, assuming it would fail:

tests are bailed on debugging and agent pod logs:

mehularora@Mehuls-Air mirrord % kubectl describe pod mirrord-agent-t4yxqj5yt6-dn29z
Name: mirrord-agent-t4yxqj5yt6-dn29z
Namespace: default
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.4
Start Time: Sun, 04 Jun 2023 11:28:41 -0400
Labels: app=mirrord
controller-uid=3f43c892-3a25-4ba1-bf55-3eee25a831ef
job-name=mirrord-agent-t4yxqj5yt6
Annotations: linkerd.io/inject: disabled
sidecar.istio.io/inject: false
Status: Pending
IP: 10.1.3.49
IPs:
IP: 10.1.3.49
Controlled By: Job/mirrord-agent-t4yxqj5yt6
Containers:
mirrord-agent:
Container ID:
Image: test
Image ID:
Port:
Host Port:
Command:
./mirrord-agent
-l
46451
--container-id
6437100db7331a00d3f9d25c8b9dd3d0810b0016f01fd71b5c8ebc21f75de9c1
--container-runtime
docker
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Requests:
cpu: 1m
memory: 1Mi
Environment:
RUST_LOG: info
MIRRORD_AGENT_STEALER_FLUSH_CONNECTIONS: true
Mounts:
/host/run from hostrun (rw)
/host/var from hostvar (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-w269w (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
hostrun:
Type: HostPath (bare host directory volume)
Path: /run
HostPathType:
hostvar:
Type: HostPath (bare host directory volume)
Path: /var
HostPathType:
kube-api-access-w269w:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message


Normal BackOff 21s (x2 over 23s) kubelet Back-off pulling image "test"
Warning Failed 21s (x2 over 23s) kubelet Error: ImagePullBackOff
Normal Pulling 10s (x2 over 23s) kubelet Pulling image "test"
Warning Failed 10s (x2 over 23s) kubelet Failed to pull image "test": rpc error: code = Unknown desc = Error response from daemon: pull access denied for test, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Warning Failed 10s (x2 over 23s) kubelet Error: ErrImagePull

@infiniteregrets infiniteregrets mentioned this pull request Jun 4, 2023
@aviramha
Copy link
Member

aviramha commented Jun 4, 2023

but in ci we use npm run test?

Copy link
Member

@aviramha aviramha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job!

@infiniteregrets
Copy link
Contributor Author

but in ci we use npm run test?

the test script in package.json is essentially the same, npm run pretest && node out/tests/runTests.js. I will run a quick test with npm run test just to be sure

@infiniteregrets
Copy link
Contributor Author

but in ci we use npm run test?

the test script in package.json is essentially the same, npm run pretest && node out/tests/runTests.js. I will run a quick test with npm run test just to be sure

works just the same, merging

@infiniteregrets infiniteregrets added this pull request to the merge queue Jun 4, 2023
Merged via the queue into metalbear-co:main with commit 70d16d5 Jun 4, 2023
@infiniteregrets infiniteregrets deleted the agent-img-issue branch June 4, 2023 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants