-
Notifications
You must be signed in to change notification settings - Fork 10
chore: release 0.38.0 #420
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
Conversation
docs/source/additional/release.rst
Outdated
|
|
||
| - The release 0.38.0 focuses on improving the security and limit the rights of the differents Substra pods when deployed on a cluster. The following changes have been made: | ||
|
|
||
| - Ressources requests and limits are now set as default for the backend and frontend. |
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.
Did we not set default values for the orchestrator?
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.
It was already all set for the orc if I'm not mistaken
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.
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.
Also I think I would reword a bit:
| - Ressources requests and limits are now set as default for the backend and frontend. | |
| - CPU and memory requests and limits are now provided by default for all orchestrator, backend and frontend pods. |
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.
Ok nice catch thanks !!
docs/source/additional/release.rst
Outdated
|
|
||
| - The profiling of functions have been reworked to take into accound the ``builiding`` step and the ``download_function`` step. | ||
|
|
||
| **Backend** |
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 is not only backend, but also orchestrator (or the title sounds confusing to me)
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.
ah my bad I thought it was only on backend, changed it
docs/source/additional/release.rst
Outdated
| - Network policies have been added to limit the communication between the different pods. | ||
| - Update the different base docker images of the Susbtra components and the the user's ones to limit their vulnerabilities. | ||
|
|
||
| - The profiling of functions have been reworked to take into accound the ``builiding`` step and the ``download_function`` step. |
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.
| - The profiling of functions have been reworked to take into accound the ``builiding`` step and the ``download_function`` step. | |
| - The profiling of functions have been reworked to take into accound the ``building`` step and the ``download_function`` step. |
|
|
||
| ### Added | ||
|
|
||
| - Documentation on how to use the Harbor profile on substra-backend ([#416](https://github.com/Substra/substra-documentation/pull/416)) |
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 am concerned there is not more added in the documentation in the light of the release notes. Did we not agree to document the NetworkPolicy part for instance? (cc @guilhem-barthes)
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 added an entry about PSS that was not included in the changelog FYI.
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.
Thank you. This should not block the release anyway, but I think we need to create follow-up issues.
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
fb0b908 to
d721803
Compare
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
Signed-off-by: ThibaultFy <thibault.fouqueray@gmail.com>
No description provided.