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

Helm chart for Kubernetes #20

Open
italolelis opened this issue May 17, 2019 · 3 comments
Open

Helm chart for Kubernetes #20

italolelis opened this issue May 17, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@italolelis
Copy link

Hello,

First of all thanks for open sourcing this great tool, I really liked the concept behind this.
I just wanted to open this issue with regards to having a helm chart that we can install in Kubernetes. I can for sure do that and open source it in the official helm repository if you don't mind.
The only requirement for this to happen is that we need most of the configurations as env vars, including the database, like stated in this issue #19 (I can also send a PR for this if you don't mind).

Maybe there would be other people interested in this.

Thanks lot!

@italolelis italolelis changed the title Helm chart for this project Helm chart for kubernetes May 17, 2019
@italolelis italolelis changed the title Helm chart for kubernetes Feature: Helm chart for Kubernetes May 17, 2019
@radiodario
Copy link

hey @italolelis we have made a kubernetes version on our fork if you want to have a look :)

@italolelis
Copy link
Author

Hey @radiodario Thanks for sharing. I've also made a helm chart for this, maybe we can combine forces here and make a PR for the upstream.

@rohitguptarspl
Copy link

rohitguptarspl commented Jul 16, 2019

Hi,
I checkout the code from kubernetes branch and getting errors in logs. Can you suggest me what is the issue.

Internal Server Error: /slack/cron_minute
response    | Traceback (most recent call last):
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
response    |     return self.cursor.execute(sql, params)
response    | psycopg2.errors.UndefinedColumn: column core_incident.reporter does not exist
response    | LINE 1: ...T "core_incident"."id", "core_incident"."report", "core_inci...
response    |                                                              ^
response    | HINT:  Perhaps you meant to reference the column "core_incident.report".
response    | 
response    | 
response    | The above exception was the direct cause of the following exception:
response    | 
response    | Traceback (most recent call last):
response    |   File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner
response    |     response = get_response(request)
response    |   File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response
response    |     response = self.process_exception_by_middleware(e, request)
response    |   File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response
response    |     response = wrapped_callback(request, *callback_args, **callback_kwargs)
response    |   File "/usr/local/lib/python3.7/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
response    |     return view_func(*args, **kwargs)
response    |   File "/app/slack/views.py", line 106, in cron_minute
response    |     handle_notifications()
response    |   File "/app/slack/decorators/incident_notification.py", line 70, in handle_notifications
response    |     for incident in open_incidents:
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 274, in __iter__
response    |     self._fetch_all()
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 1242, in _fetch_all
response    |     self._result_cache = list(self._iterable_class(self))
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/models/query.py", line 55, in __iter__
response    |     results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/models/sql/compiler.py", line 1100, in execute_sql
response    |     cursor.execute(sql, params)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 99, in execute
response    |     return super().execute(sql, params)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute
response    |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
response    |     return executor(sql, params, many, context)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
response    |     return self.cursor.execute(sql, params)
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/utils.py", line 89, in __exit__
response    |     raise dj_exc_value.with_traceback(traceback) from exc_value
response    |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
response    |     return self.cursor.execute(sql, params)
response    | django.db.utils.ProgrammingError: column core_incident.reporter does not exist
response    | LINE 1: ...T "core_incident"."id", "core_incident"."report", "core_inci...
response    |                                                              ^
response    | HINT:  Perhaps you meant to reference the column "core_incident.report".
response    | 
response    |  ERROR - log        - Internal Server Error:

Also I am looking for Helm chart for Kubernetes.

@milesbxf milesbxf added the enhancement New feature or request label Aug 14, 2019
@milesbxf milesbxf changed the title Feature: Helm chart for Kubernetes Helm chart for Kubernetes Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants