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

Cronjob version configurable #88

Open
acevedomiguel opened this issue Feb 28, 2024 · 3 comments
Open

Cronjob version configurable #88

acevedomiguel opened this issue Feb 28, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@acevedomiguel
Copy link

I'm using the latest version of EKS on AWS and wanted to deploy some jobs on benthos.

It seems to try to create a batch/v1beta1, but the latest version of EKS has batch/v1. There is any way to configure this?

Received response status [FAILED] from custom resource. Message returned: Error: b'configmap/benthos-streams configured\nerror: error retrieving RESTMappings to prune: invalid resource batch/v1beta1, Kind=CronJob, Namespaced=true: no matches for kind "CronJob" in version "batch/v1beta1"\n'

let me know if you need more information

@charlie-haley
Copy link
Collaborator

Hey, thanks for raising this!

Could you send me an examples of the values you're using with the Helm Chart?

@charlie-haley charlie-haley added the bug Something isn't working label Feb 29, 2024
@acevedomiguel
Copy link
Author

Hi Charlie, thanks for your answer, here is my values.yaml

deployment:
  replicaCount: 1
  podAnnotations: {}
  podLabels: {}
  annotations: {}
  terminationGracePeriodSeconds: 60
  rolloutConfigMap: true

  readinessProbe:
    failureThreshold: 1
    periodSeconds: 5
    successThreshold: 1
    timeoutSeconds: 2
    httpGet:
      path: /ready
      port: http
  livenessProbe:
    failureThreshold: 3
    periodSeconds: 5
    successThreshold: 1
    timeoutSeconds: 2
    httpGet:
      path: /ping
      port: http
commonLabels: {}

image:
  repository: 'jeffail/benthos'
  pullPolicy: IfNotPresent
  tag: ''

imagePullSecrets: []
nameOverride: ''
fullnameOverride: ''

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

podSecurityContext:
  {}

securityContext:
  {}

service:
  name: http
  type: ClusterIP
  port: 80
  targetPort: http
  protocol: TCP

  extraPorts:

ingress:
  enabled: false
  className: ''
  annotations:
    {}
  hosts: []
  tls: []

env: []

envFrom:
  []

resources:
  {}

autoscaling:
  enabled: false
  minReplicas: 1
  maxReplicas: 12
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 80

nodeSelector: {}

tolerations: []

affinity: {}

podDisruptionBudget:
  enabled: false
  
initContainers: []

updateStrategy: {}

extraVolumes:
  []

extraVolumeMounts:
  []

streams:
  enabled: false
  streamsConfigMap: 'benthos-streams' # refers to ConfigMap in streamconfig.yml
  api:
    enable: true

http:
  # Disabling HTTP server will prevent service and ingress objects from being created.
  enabled: true
  address: '0.0.0.0:4195'
  root_path: '/benthos'
  debug_endpoints: false
  cors:
    enabled: false

serviceMonitor:
  enabled: false
  interval: '10s'
  scheme: http

command: []

args: []

watch: false

topologySpreadConstraints: []

config: {}

@acevedomiguel
Copy link
Author

acevedomiguel commented Mar 3, 2024

the base example works right out of the box

input:
  generate:
    mapping: root = "woof"
    interval: 30s
    count: 0

buffer:
  memory: {}

pipeline:
  processors: []

output:
  stdout:
    codec: lines

but once we want to create a real-world project, it returns the error mentioned:
I removed the processors and outputs to test. The error it's triggered by just trying to setup a sqs input.

input:
  label: "raw_values_sqs"
  aws_sqs: 
    url: "https://sqs.ap-northeast-1.amazonaws.com/1234567890/MySqs"
    region: "ap-northeast-1"
    max_number_of_messages: 10

pipeline:
  processors: []

output:
  stdout:
    codec: lines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants