Git Product home page Git Product logo

charts's Introduction

Hi there ๐Ÿ‘‹

I'm 0hlov3, a passionate DevOps engineer and developer from Germany

  • ๐ŸŒฑ Iโ€™m currently learning vue and i'm looking forward to get my cks

  • ๐Ÿ“ I regularly write articles on https://blog.schoenwald.aero

โœ๏ธ Blogs posts

๐Ÿ—ฃ๏ธ Connect with me

0hlov3 0hlov3 0hlov3s 0hlov3 @0hlov3

๐Ÿ› ๏ธ Technologies & Tools

linux macos
bash zsh
IntelliJ IDEA VS Code vim
microsoftazure hetzner digitalocean
postgresql MariaDB Cassandra
go python vue.js html5 css3 sass
docker kubernetes red-hat-open-shift helm terraform ansible vagrant elasticsearch Prometheus grafana jenkins postman

charts's People

Contributors

0hlov3 avatar l-ra avatar

Stargazers

 avatar  avatar

Watchers

 avatar

Forkers

l-ra

charts's Issues

[gotosocial] Add support for arbitary initContainers

Is your feature request related to a problem ?

I'd like to be able to configure some networking stuff in my gotosocial container via an initContainer before the main container starts.

Describe the solution you'd like.

I'd like an additional value/set of values in the values.yaml that gets translated into the gotosocial deployment's initContainers field

Describe alternatives you've considered.

Forking the chart seems to be the only alternative for what I want to do with this, as network policies don't support blocking cidrs.

Additional context.

No response

[gotosocial] non fuctional sqlite in default setup

Describe the bug a clear and concise description of what the bug is.

After almost default chart install with both local and external postgres disabled the server does not start with following error:

timestamp="06/08/2023 07:53:39.871" func=cache.(*Caches).Init level=INFO msg="init: 0xc00090e000"
timestamp="06/08/2023 07:53:39.871" func=cache.(*Caches).Start level=INFO msg="start: 0xc00090e000"
timestamp="06/08/2023 07:53:39.872" func=bundb.sqliteConn level=INFO msg="connected to SQLITE database with address file:/gotosocial/storage/sqlite.db?_txlock=immediate"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma journal_mode set to wal"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma synchronous set to 1"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma cache_size set to -8192"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma busy_timeout set to 1800000"
timestamp="06/08/2023 07:53:39.939" func=bundb.doMigration level=INFO msg="there are no new migrations to run"
2023/08/06 07:53:40 error executing command: error creating instance account: disk I/O error (6410)
timestamp="06/08/2023 07:53:40.247" func=cache.(*Caches).Stop level=INFO msg="stop: 0xc00090e000"

What's your helm version?

3.8.2

What's your kubectl version?

1.23.5

Which chart?

gotosocial

What's the chart version?

0.4.8

What happened?

After almost default chart install with both local and external postgres disabled the server does not start with following error:

timestamp="06/08/2023 07:53:39.871" func=cache.(*Caches).Init level=INFO msg="init: 0xc00090e000"
timestamp="06/08/2023 07:53:39.871" func=cache.(*Caches).Start level=INFO msg="start: 0xc00090e000"
timestamp="06/08/2023 07:53:39.872" func=bundb.sqliteConn level=INFO msg="connected to SQLITE database with address file:/gotosocial/storage/sqlite.db?_txlock=immediate"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma journal_mode set to wal"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma synchronous set to 1"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma cache_size set to -8192"
timestamp="06/08/2023 07:53:39.935" func=bundb.sqlitePragmas level=INFO msg="sqlite pragma busy_timeout set to 1800000"
timestamp="06/08/2023 07:53:39.939" func=bundb.doMigration level=INFO msg="there are no new migrations to run"
2023/08/06 07:53:40 error executing command: error creating instance account: disk I/O error (6410)
timestamp="06/08/2023 07:53:40.247" func=cache.(*Caches).Stop level=INFO msg="stop: 0xc00090e000"

What you expected to happen?

Server starts normally

How to reproduce it?

Install chart with default config with sqlite database option (both postgres disables)

Enter the changed values of values.yaml?

# subchart 
gotosocial:

  image:
    repository: superseriousbusiness/gotosocial
    pullPolicy: IfNotPresent

  replicaCount: 1

  ingress:
    enabled: true
    className: "nginx"
    annotations: 
      cert-manager.io/cluster-issuer: letsencrypt-issuer
      nginx.ingress.kubernetes.io/proxy-body-size: 10000m
      nginx.org/client-max-body-size: 10000m 
    hosts:
      - host: REDACTED
        paths:
          - path: /
            pathType: ImplementationSpecific
    tls: 
    - secretName: REDACTED-tls
      hosts:
      - REDACTED

  resources:
    limits:
      cpu: 500m
      memory: 512Mi
    requests:
      cpu: 500m
      memory: 512Mi

  gotosocial:
    strategy:
      type: Recreate
    persistence:
      enabled: true
      accessMode: "ReadWriteOnce"
      size: "10Gi"
      #storageClass: ""
    config:
      #logLevel: "info"
      #logDBQueries: ""
      applicationName: "gotosocial"
      host: "REDACTED"
      accountDomain: "REDACTED"
      trustedProxies:
        - "10.0.0.0/8"
        - "172.16.0.0/12"
        - "192.168.0.0/16"
      web:
        templateBaseDir: "./web/template/" 
        assetBaseDir: "./web/assets/"

  postgresql:
    enabled: false

  externalPostgresql:
    enabled: false
    database: GoToSocial

  serviceAccount:
    create: true
    annotations: {}
    name: ""

  podAnnotations: {}

  podSecurityContext:
    runAsUser: 1000
    runAsGroup: 1000
    fsGroup: 1000

  securityContext:
    capabilities:
      drop: 
        - ALL
    readOnlyRootFilesystem: true
    allowPrivilegeEscalation: false
    runAsNonRoot: true
    runAsUser: 1000
    runAsGroup: 1000

  nodeSelector: {}

  tolerations: []

  affinity: {}

Enter the command that you execute and failing/misfunctioning.

in context of chart which has goosocial as dependency

helm -n REDACETD install default . -f values.yaml 

Anything else we need to know?

According to sqlite doc the error 6410 is a problem with temp file creation as described here https://www.sqlite.org/rescode.html#ioerr_gettemppath

Can be fixed with SQLITE_TMPDIR targeted to the same folder which is used for sqlite.db file

I'll try to send pull request

Duplicated Sqlite configuration

Hello there!
First of all, thanks for your work1

This issue is regarding some duplicated configuration when using sqlite. The next lines are the ones from 66 to 76.

In the lines 74 to 76 there should only be configuration that is common in all databases (as far as I understand). But t here's also configuration from sqlite, as in the lines 69 to 71.

    {{- else }}
    db-type: sqlite
    db-address: {{ .Values.gotosocial.config.db.sqliteAddress | default "/gotosocial/storage/sqlite.db" |quote}}
    db-sqlite-journal-mode: {{ .Values.gotosocial.config.db.sqliteJournalMode | default "WAL" |quote }}
    db-sqlite-synchronous: {{ .Values.gotosocial.config.db.sqliteSynchronous | default "NORMAL" |quote }}
    db-sqlite-cache-size: {{ .Values.gotosocial.config.db.sqliteCacheSize | default "8MiB" |quote }}
    db-sqlite-busy-timeout: {{ .Values.gotosocial.config.db.sqliteBusyTimeout | default "5m" |quote }}
    {{- end }}
    db-max-open-conns-multiplier: {{ .Values.gotosocial.config.db.maxOpenConnsMultiplier | default 8 }}
    db-sqlite-synchronous: {{ .Values.gotosocial.config.db.sqliteSynchronous | default "NORMAL" | quote }}
    db-sqlite-cache-size: {{ .Values.gotosocial.config.db.sqliteCacheSize | default "8MiB" | quote }}
    db-sqlite-busy-timeout: {{ .Values.gotosocial.config.db.sqliteBusyTimeout | default "5m" | quote }}

This causes to GTS to not start, with the next error:

2023/06/21 08:55:20 error executing command: error reloading config: While parsing config: yaml: unmarshal errors:
  line 46: mapping key "db-sqlite-synchronous" already defined at line 42
  line 47: mapping key "db-sqlite-cache-size" already defined at line 43
  line 48: mapping key "db-sqlite-busy-timeout" already defined at line 44

I believe that the issue would be solved by just deleting the lines 73 to 76.

Kind regards.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.