-
Notifications
You must be signed in to change notification settings - Fork 70
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
Remove Knative #661
Remove Knative #661
Conversation
ed3c015
to
45fcf26
Compare
deploy/k8s/minio.yml.j2
Outdated
@@ -11,7 +11,7 @@ metadata: | |||
spec: | |||
containers: | |||
- name: minio-main | |||
image: faasm/minio:0.8.12 | |||
image: faasm/minio:{{ faasm_version }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that, given that we were already templating some of the contents, it was cleaner to also template the faasm version, instead of updating all deployment files every time we bump the code version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What other contents are we templating? I had thought I'd removed all templating from the repo as it makes it difficult to review changes, and generally adds more complexity. With this change we're now mixing SGX and non-SGX files again which I'd also quite like to avoid (just to keep the standard non-SGX setup as simple as possible).
@@ -1,8 +1,8 @@ | |||
from time import sleep | |||
from datetime import datetime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very messy diff. You may check the raw file here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, other than the templating which I'm not sure about. Happy to discuss offline.
deploy/k8s/minio.yml.j2
Outdated
@@ -11,7 +11,7 @@ metadata: | |||
spec: | |||
containers: | |||
- name: minio-main | |||
image: faasm/minio:0.8.12 | |||
image: faasm/minio:{{ faasm_version }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What other contents are we templating? I had thought I'd removed all templating from the repo as it makes it difficult to review changes, and generally adds more complexity. With this change we're now mixing SGX and non-SGX files again which I'd also quite like to avoid (just to keep the standard non-SGX setup as simple as possible).
faasmcli/faasmcli/tasks/k8s.py
Outdated
{ | ||
"name": "AZ_ATTESTATION_PROVIDER_URL", | ||
"value": "https://faasmattprov.eus2.attest.azure.net", | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we were going to template this stuff, it might be cleaner to keep this in a YAML file, but wrap it with an {% if sgx %}
to switch it on or off.
4d814e0
to
2a83a8b
Compare
@Shillaker do you think we can merge this in? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, sorry for the delay. LGTM 👍
In this PR we remove our integration with Knative. We were not using any of Knative's features, and it was making the deployment more complex, slow, and verbose.
In contrast, now we deploy Faasm on a bare k8s cluster. This simplifies the installation and deployment scripts. In summary, deploying/removing Faasm from an existing k8s cluster is a one-liner:
I think I have removed all dangling references to Knative in the org (but I am surely missing some). See related PRs: faasm/experiment-base#51, faasm/experiment-faabric#32, faasm/experiment-openmp#18