https://dagster.io/ logo
#ask-community
Title
# ask-community
m

Mohan Ganeshan

03/31/2023, 6:13 AM
we basically have 2 separate devops project to manage the Dagster infra and Dagster usercode , we made deployment using subchart:false and workspace enabled: true, in this scenario we end up getting 2 helm release - one for Dagster infra as "DAGSTER" release and another one for Dasgter usercode as "DAGSTER-USER-DEPLOYMENTS" release. But, ideally we are looking to use existing DAGSTER release (Dagster Infra) to deploy the User code without getting created the new HELM release. support i am looking here is: do we have possible scope to deploy two separate helm chart into existing single helm release? Dasgster chart and Dasgter-user-deployment chart both should be installed or upgraded into single release. We also have tried to upgrade the existing helm release in the usercode deployment pipeline by using Usercode-deployment chart but it completely removed the Dagit and Daemon, and revised the version of the release which resulted by just having the usercode in the cluster and missing the dagit and daemon. Please help us or confirm the possible approach we can use for deployment?
d

daniel

03/31/2023, 2:34 PM
Hi Mohan - Unfortunately I think the only two options here right now are to use one helm chart and one release or two helm charts and two releases. If you're using a single helm chart and a single release, you should still be able to do an upgrade of just the user code deployments, but all your values would need to be in a single values.yaml file
a

Adam Bloom

03/31/2023, 3:51 PM
With two releases, you should be able to upgrade them separately - I don't quite understand your comment about upgrading usercode removing dagit and daemon. We deploy with two deployments and have never seen that happen.
m

Mohan Ganeshan

04/03/2023, 1:44 PM
Thank you Daniel and Adam for clarifying the approach
I am facing the below error while I am trying to install the SQL server:
Copy code
sqlalchemy.exc.DBAPIError: (pyodbc.Error) ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'SQL Server Native Client 11.0' : file not found (0) (SQLDriverConnect)")
(Background on this error at: <https://sqlalche.me/e/14/dbapi>)
My docker file looks like this: FROM docker-images.artifactory.danskenet.net/db/python:3.7-slim-buster ARG ENV DEBIAN_FRONTEND noninteractive LANGUAGE=C.UTF-8 LANG=C.UTF-8 LC_ALL=C.UTF-8 \ LC_CTYPE=C.UTF-8 LC_MESSAGES=C.UTF-8 ARG DAGSTER_VERSION=0.15.5 ARG DAGSTER_UID=50000 ARG DAGSTER_HOME=/opt/dagster/dagster_home # Install curl and gnupg2 RUN apt-get update \ && apt-get install -y --no-install-recommends \ curl apt-utils apt-transport-https debconf-utils gcc \ gnupg2 \ build-essential \ unixodbc-dev \ && apt-get -y install unixodbc unixodbc-dev \ && apt-get autoremove -yqq --purge \ && apt-get clean \ && rm -rf /var/lib/apt/lists/* RUN echo 'deb [arch=amd64] https://artifactory.danskenet.net/artifactory/remote-debian-microsoft/debian/10/prod buster main' > /etc/apt/sources.list.d/mssql-release.list RUN curl https://artifactory.danskenet.net/artifactory/remote-debian-microsoft/keys/microsoft.asc | apt-key add - RUN apt-get update -yqq RUN apt-get upgrade -yqq RUN ACCEPT_EULA=Y apt-get -yqq install -y --no-install-recommends --allow-unauthenticated msodbcsql17 mssql-tools unixodbc-dev libgssapi-krb5-2 RUN rm -rf /var/lib/apt/lists/* RUN echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc RUN /bin/bash -c "source ~/.bashrc" RUN apt-get autoremove -yqq --purge RUN apt-get clean && rm -rf /var/lib/apt/lists/* RUN pip install --upgrade pip \ dagster==${DAGSTER_VERSION} \ dagster-postgres==${DAGSTER_VERSION} \ dagster-aws==${DAGSTER_VERSION} \ dagster-k8s==${DAGSTER_VERSION} \ dagster-celery[flower,redis,kubernetes]==${DAGSTER_VERSION} \ dagster-celery-k8s==${DAGSTER_VERSION} \ dagster_pandas \ dagster_pandera \ importlib-metadata\<5.0 \ sqlalchemy\<2.0.0 \ pandas \ pandera \ pyodbc # Get example pipelines COPY examples/deploy_k8s/mydagster /mydagster RUN adduser --gecos "First Last,RoomNumber,WorkPhone,HomePhone" --disabled-password \ --quiet "dagster" --uid "${DAGSTER_UID}" --gid "0" --home "${DAGSTER_HOME}" \ # Make Airflow files belong to the root group and are accessible. This is to accommodate the guidelines from # OpenShift https://docs.openshift.com/enterprise/3.0/creating_images/guidelines.html && mkdir -pv "${DAGSTER_HOME}" \ && chown -R dagster:0 "${DAGSTER_HOME}" \ && chmod -R g+rw "${DAGSTER_HOME}" \ && find "${DAGSTER_HOME}" -executable -print0 | xargs --null chmod g+x \ && mkdir -pv "${DAGSTER_HOME}/storage" \ && chown -R dagster:0 "${DAGSTER_HOME}/storage" \ && chmod -R g+rw "${DAGSTER_HOME}/storage" RUN chmod g=u /etc/passwd \ && usermod -g 0 dagster -G 0 # Lower the TLS to 1 as CIL seems to be running 1. RUN sed -i 's/TLSv1.2/TLSv1/g' /etc/ssl/openssl.cnf && \ sed -i 's/SECLEVEL=2/SECLEVEL=1/g' /etc/ssl/openssl.cnf USER ${DAGSTER_UID}
please advice/suggest me to fix it